[Issue 3567] std.traits: Unqual strips qualifiers on structs with references that would break const/immutable.

2019-12-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3567 berni44 changed: What|Removed |Added CC||issues.dl...@jmdavisprog.co |

[Issue 3567] std.traits: Unqual strips qualifiers on structs with references that would break const/immutable.

2018-07-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3567 --- Comment #9 from Steven Schveighoffer --- I think a trait "ForceUnqual" may be needed in some cases, but "Unqual" I have always expected to behave the way it does (except in the case of structs containing references, for which it should not strip

[Issue 3567] std.traits: Unqual strips qualifiers on structs with references that would break const/immutable.

2018-07-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3567 --- Comment #8 from Timoses --- (In reply to Steven Schveighoffer from comment #6) > Note, the bug here in FeepingCreature's case is that it strips more than it > should. It is supposed to be safe to use Unqual. > > So the expectation that Unqual

[Issue 3567] std.traits: Unqual strips qualifiers on structs with references that would break const/immutable.

2018-07-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3567 --- Comment #7 from Timoses --- (In reply to Steven Schveighoffer from comment #6) > I'm changing the title accordingly. Perhaps we should actually close this > bug and open another, as the whole issue has really been flipped around? Perhaps you're

[Issue 3567] std.traits: Unqual strips qualifiers on structs with references that would break const/immutable.

2018-07-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=3567 Steven Schveighoffer changed: What|Removed |Added Summary|std.traits: Unqual doesn't |std.traits: Unqual strips