Explaining why something isn't safe

H. S. Teoh hsteoh at quickfur.ath.cx
Mon Aug 16 14:03:44 UTC 2021


On Mon, Aug 16, 2021 at 01:29:05PM +0000, bauss via Digitalmars-d wrote:
> On Monday, 16 August 2021 at 13:05:48 UTC, Adam D Ruppe wrote:
> > On Monday, 16 August 2021 at 12:51:26 UTC, Steven Schveighoffer wrote:
> > > This just came up in a discussion, and I've thought about this in
> > > the past, so it might have already come up.
> > 
> > Forum threads are ephemeral. Add to bugzilla plz. Then it will never
> > be forgotten....
> > 
> > https://issues.dlang.org/show_bug.cgi?id=17374
> > 
> > .... or acted upon. 4 years and counting.
> 
> Damn 4 years... I think it would be a really nice addition. Especially
> for people who aren't used to @safe and I can imagine a lot of people
> just skip using it because the hassle isn't worth it.

I've been mostly ignoring @safe, and this is one of the reasons: it's
just too annoying to use sometimes.  With long UFCS chains the current
error messages just aren't helpful in finding the problem.  If this was
fixed I'd be more inclined to use @safe.


T

-- 
Not all rumours are as misleading as this one.


More information about the Digitalmars-d mailing list