[Issue 22387] Noreturn init loses type qualifiers
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Thu Oct 14 14:42:56 UTC 2021
https://issues.dlang.org/show_bug.cgi?id=22387
Dlang Bot <dlang-bot at dlang.rocks> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Dlang Bot <dlang-bot at dlang.rocks> ---
dlang/dmd pull request #13168 "Fix 22387 - Don't unconditionally override the
type of an assert" was merged into master:
- e49e29a909578009e554b6ad9f01453c2c6628be by MoonlightSentinel:
Fix 22387 - Don't unconditionally override the type of an assert
The type might've already been set before, e.g. by `defaultInitLiteral`
for `const(noreturn).init`. Unconditionally setting the type to
`noreturn` would discard qualifiers and the cause problems in generic
code, e.g. for `isBidirectionalRange!(const(noreturn)[])`.
https://github.com/dlang/dmd/pull/13168
--
More information about the Digitalmars-d-bugs
mailing list