DMD 1.027 and 2.011 releases

[Christopher Wright]

Georg Wrede wrote:
> Walter Bright wrote:
>> Graham St Jack wrote:
>>
>>> It will be a good trick if you can pull it off. I don't see how it 
>>> can be done without examining the source code of all the called 
>>> functions, leaving us back where we started with throw specs.
>>>
>>> The C++ approach of a runtime check isn't perfect, but at least it 
>>> can be done, and provides a more definite form of documentation than 
>>> comments.
>>
>>
>> Are you sure it does a runtime check for nothrow?
>>
>>> If the static checks aren't done well enough and runtime checks 
>>> aren't done at all, I would prefer to rely on comments.
> 
> IMHO, it would behoove the compiler to keep track of possible/potential 
> exceptions a function can throw. (Just as well as (again, IMHO) it would 
> behoove the compiler to keep track of functions that /potentially/ have 
> side effects.)

There's a few problems with what you're asking for:
- extern(D)
- .di files
- delegates
- dynamic loading

There's also the matter of executable bloat.