[Issue 904] Bad code generated for local _assert routine

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=904


sean at f4.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Comment #2 from sean at f4.ca  2007-01-31 02:02 -------
But surely that is no reason to generate invalid code.  What if the user wants
to halt the debugger on an assert via int 3, and optionally continue
afterwords?  Or report assertion failures during unit testing without littering
the code with try/catch blocks?  I am concerned because this change broke code
that has been in place and working for two years, and there seems no rational
explanation for the change.


--