January 02, 2022 [Issue 22644] Using @disable on enum members produces unrelated errors | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=22644 moonlightsentinel@disroot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |moonlightsentinel@disroot.o | |rg Hardware|x86 |All Resolution|--- |INVALID OS|Mac OS X |All --- Comment #1 from moonlightsentinel@disroot.org --- The template instance for `writefln` has no knowledge about the value passed in the provided snipped and hence has to accommodate for each possible value of `Foo`. So at most this is an enhancement for Phobos to skip disabled enum members. -- |
January 03, 2022 [Issue 22644] Using @disable on enum members produces unrelated errors | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=22644 Tejas_Garhewal <scienticman@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scienticman@gmail.com --- Comment #2 from Tejas_Garhewal <scienticman@gmail.com> --- I understand that this issue has been declared resolved, but a workaround until the underlying issue is solved(via enhancing phobos or something else) is to use stringof property ```d enum Foo { x = 7, @disable y = 8, } void main() { writefln("Hello %s", Foo.x.stringof); } ``` It also correctly fails to compile if you write Foo.y.stringof -- |
Copyright © 1999-2021 by the D Language Foundation