[Issue 20328] [REG 2.089 beta] deprecation message about Nullable.get in isInputRange

d-bugmail at puremagic.com d-bugmail at puremagic.com
Tue Oct 29 06:27:34 UTC 2019


--- Comment #10 from FeepingCreature <default_357-line at yahoo.de> ---
And of course, I had it completely wrong - Nullable!string *is* actually an
input range... because string is. Obviously! >.<

So the deprecation was actually entirely valid aside the fact that it was total
bunk because format doesn't ever hit that branch, it just uses Nullable's
toString overload. So the fix was reordering the conditions in the format
string check to match the order in the actual format code, ie. it notices that
there's a toString function and doesn't even check for input rangeness.


More information about the Digitalmars-d-bugs mailing list