https://issues.dlang.org/show_bug.cgi?id=20328

--- Comment #10 from FeepingCreature <default_357-line@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.

--

https://issues.dlang.org/show_bug.cgi?id=20328

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #11 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/phobos pull request #7257 "Fix issue 20328: only check isInputRange when we've already excluded toString overload." was merged into stable:

- 0656d0683bbce88199471f6753b35997f16ec243 by Mathis Beer:
  Fix issue 20328: only check isInputRange when we've already excluded toString
overloads

https://github.com/dlang/phobos/pull/7257

--

https://issues.dlang.org/show_bug.cgi?id=20328

Basile-z <b2.temp@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dlang-bugzilla@thecybershad
                   |                            |ow.net

--- Comment #12 from Basile-z <b2.temp@gmx.com> ---
*** Issue 20265 has been marked as a duplicate of this issue. ***

--