https://issues.dlang.org/show_bug.cgi?id=14387
Nick Treleaven changed:
What|Removed |Added
CC||temta...@gmail.com
--- Comment #7 from
|--- |FIXED
--- Comment #6 from Dlang Bot ---
dlang/dmd pull request #15860 "Deprecate string literals as (static) assert
conditions" was merged into master:
- 55d0483a5d5ceef59327cde7cb12124d98547459 by Nick Treleaven:
Deprecate string literals as assert conditions
Fix I
https://issues.dlang.org/show_bug.cgi?id=14387
--- Comment #5 from Dlang Bot ---
@ntrel created dlang/dmd pull request #15860 "Deprecate string literals as
(static) assert conditions" fixing this issue:
- Deprecate string literals as assert conditions
Fix Issue 14387 - Disal
created dlang/dmd pull request #15837 "Deprecate boolean evaluation of
array/string literals" fixing this issue:
- Deprecate boolean evaluation of array/string literals
Fix Issue 14387 - Disallow string literals as assert conditions.
https://github.com/dlang/dmd/pull/15837
--
https://issues.dlang.org/show_bug.cgi?id=14387
Iain Buclaw changed:
What|Removed |Added
Priority|P1 |P4
--
https://issues.dlang.org/show_bug.cgi?id=14387
Nick Treleaven changed:
What|Removed |Added
CC||n...@geany.org
--- Comment #3 from Nick
https://issues.dlang.org/show_bug.cgi?id=14387
Vladimir Panteleev thecybersha...@gmail.com changed:
What|Removed |Added
CC|
https://issues.dlang.org/show_bug.cgi?id=14387
--- Comment #1 from Don clugd...@yahoo.com.au ---
The spec says:
As a debugging tool, the compiler may insert checks to verify that the
condition indeed holds by evaluating AssignExpression at runtime. If it
evaluates to a non-null class reference,
