Check demand signatures for catchRetry# and catchSTM#

#13330 (closed) was fixed by giving catch# a different (simpler and more honest) demand signature. Are the signatures for catchRetry# and catchSTM# similarly problematic? We need to check.

Trac metadata

Trac field	Value
Version	8.0.1
Type	Task
TypeOfFailure	OtherFailure
Priority	normal
Resolution	Unresolved
Component	Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture

mentioned in issue #13330 (closed)

changed milestone to %8.2.1

changed weight to 5

added Ttask Trac import labels

Trac metadata

Trac field	Value
Differential revisions	- → D3263

closed

This was resolved for catchSTM# in 6a94b8bb. dfeuer, have you confirmed that catchRetry# is alright?

Trac metadata

Trac field	Value
Resolution	Unresolved → ResolvedFixed

reopened

No, I left catchRetry# alone, and can't vouch for it. Let me consider it a bit.

Trac metadata

Trac field	Value
Resolution	ResolvedFixed → Unresolved

changed milestone to %8.4.1

Bumping off to 8.4

mentioned in issue #13977 (closed)

changed milestone to %8.6.1

This ticket won't be resolved in 8.4; remilestoning for 8.6. Do holler if you are affected by this or would otherwise like to work on it.

This will not be addressed in GHC 8.6.

changed milestone to %8.8.1

These will not be addressed in GHC 8.6.

changed milestone to %8.10.1

Bumping milestones of low-priority tickets.

added exceptions label

added Pnormal label

removed milestone