I think a hard crash is completely appropriate. Bound violations are
#15092: Optionally bounds-check primops -------------------------------------+------------------------------------- Reporter: dfeuer | Owner: (none) Type: feature request | Status: new Priority: normal | Milestone: 8.6.1 Component: Compiler | Version: 8.2.2 (CodeGen) | Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by dfeuer): Replying to [comment:1 Lemming]: programming errors thus there is no way to safely recover from them, anyway. My concerns about the "hard crash" approach: the error messages may not be as informative as one might wish, it may be tough to get the error messages in some environments, and I don't know if there would be any challenges ensuring that other application threads get killed. But I do think it would be a lot better to have that as an option than to have nothing. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/15092#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler