#1171: GHC doesn't respect the imprecise exceptions semantics
--+-
Reporter: neil | Owner:
Type: bug | Status: reopened
Priority: low | Milestone: _|_
#1171: GHC doesn't respect the imprecise exceptions semantics
--+-
Reporter: neil | Owner:
Type: bug | Status: reopened
Priority: low | Milestone: _|_
Hi
In response to Neil: why use `unsafePerformIO` rather than IO exceptions
here? I think you're asking for more trouble...
Are you referring to ioError? My knowledge of exceptions in Haskell is limited.
The error architecture is often a long way from the IO monad, so
whatever we do can't
Neil Mitchell wrote:
Hi
In response to Neil: why use `unsafePerformIO` rather than IO exceptions
here? I think you're asking for more trouble...
Are you referring to ioError? My knowledge of exceptions in Haskell is
limited.
The error architecture is often a long way from the IO monad,
Hello,
The code in YHC is roughly if some list is empty then error No files found
else error Many files found. If this code were changed to the equivalent
of error (if some list is empty then No files found else Many files
found), would there still be circumstances where the actual output
The code in YHC is roughly if some list is empty then error No files
found
else error Many files found. If this code were changed to the
equivalent
of error (if some list is empty then No files found else Many files
found), would there still be circumstances where the actual output
produced
Simon Marlow wrote:
The code in YHC is roughly if some list is empty then error No files
found
else error Many files found. If this code were changed to the
equivalent
of error (if some list is empty then No files found else Many files
found), would there still be circumstances where the actual
Simon Marlow wrote:
Simon Marlow wrote:
The code in YHC is roughly if some list is empty then error No files
found
else error Many files found. If this code were changed to the
equivalent
of error (if some list is empty then No files found else Many files
found), would there still be
