On 28.06.2010 01:09, Andrei Alexandrescu wrote: [...]
We haven't reached consensus on where to put enforce() and friends. Any other ideas? Of the above, I like std.checks.Better yet, how about defining std.exception that includes a host of exception-related functionality (such as defining exceptions that retain file and line, perhaps stack traces etc.)?
How will std.exception relate to core.exception? Seems to me having two module with that similiar names could easily be confusing.
