https://issues.dlang.org/show_bug.cgi?id=20328
--- Comment #10 from FeepingCreature <[email protected]> --- 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. --
