On Tuesday, 20 January 2015 at 18:25:42 UTC, ketmar via
Digitalmars-d wrote:
how likely this to be changed? is there *any* chances of that
in 2015?
2016? and why we can't just remove that restriction when new GC
will be
implemented? removing the "@nogc" requirement on class dtors
will break
*nothing* *at* *all*. yet adding it now, while we don't have
that new
GC, will prevent alot of bugs that can slip in crack.
btw, you won the prize of not talking about "broken code"!
sadly, i
forgot to setup the prizes... anyway, thanks for sane argument.
Is it that subtle of a bug? Your program crashes once, you go on
the forums and find the answer, and then you know never to do it
again.
