Steven Schveighoffer <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #8 from Steven Schveighoffer <> 2012-05-24 
07:01:45 PDT ---
(In reply to comment #4)
> FWIW, I'm all for making Errors actually fatal and terminating the runtime
> immediately, but then OutOfMemory*Error* HAS GOT TO GO.

Then you could mark almost nothing as nothrow.

I think OutOfMemory should be an error.  If you want to override the behavior
because you have special circumstances, that should be possible (i.e. somehow
prevent out of memory error from being thrown, but instead handle the situation
in a different way).

What about an enhancement of adding GC.mallocNoError and friends which instead
return null when a memory block is not available instead of throwing?

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to