[Issue 23266] Dead else blocks are not considered unreachable

2023-11-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23266 FeepingCreature changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 23266] Dead else blocks are not considered unreachable

2023-11-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23266 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@gmail.com --- Comment #3

[Issue 23266] Dead else blocks are not considered unreachable

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23266 Iain Buclaw changed: What|Removed |Added Priority|P1 |P4 --

[Issue 23266] Dead else blocks are not considered unreachable

2022-07-22 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23266 --- Comment #2 from FeepingCreature --- I've tried a DMD branch that errors with -w if `if()` has a statically known true condition and an else block. The two main things I ran into in Phobos are: 1. if (false) { some code that should affect

[Issue 23266] Dead else blocks are not considered unreachable

2022-07-22 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23266 --- Comment #1 from FeepingCreature --- One could argue that this is correct because otherwise the common technique of stubbing out an if statement by adding `if (false &&` stops working. For the CompoundStatement error to trigger with that, you'd