[Issue 14544] isForwardRange failed to recognise valid forward range

via Digitalmars-d-bugs digitalmars-d-bugs at puremagic.com
Mon May 4 12:23:55 PDT 2015


https://issues.dlang.org/show_bug.cgi?id=14544

--- Comment #3 from Jonathan M Davis <issues.dlang at jmdavisProg.com> ---
Oh, it's stupid that save is required to be a property, since it's not at all
an abstraction for a variable, but I don't think that Andrei really understands
the idea behind properties (certainly, he didn't when he made save a property,
and I also think that that's why he's generally been unhappy with @property
when it's come up). The problem is though that once it's required to be a
property, changing it later risks breaking code. Given how poorly properties
are checked by the compiler, we _might_ be able to make the change, but we'd
have to be careful about it. Regardless, the fact that isForwardRange is the
way it is and requires that save be a property is very much on purpose.

--


More information about the Digitalmars-d-bugs mailing list