Re: ReflectionType::__toString() prepending \ to class names

I still want to see code that outweights these commonly used open-source tools before you grab that argument again. As also said by Dan: new features => adaptation required. Supporting ? in your own home-grown internal code-generator is something you can do as part of a 7.1 migration path, exactly like we'll have to do with the OSS libs. That said, I'm muting the thread: I'm basically wasting time with this, apparently. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On Sun, Aug 21, 2016 at 9:48 PM, Levi Morrison <levim@php.net> wrote: > The issue here is around changes that affect old features (__toString), >> where the behavior changes depending on whether a parameter is defaulted or >> not (also a previously existing feature) >> > > Which has existed for only one release. This is a small BC break and is > intended. We previously had nullable types just no way to really encode it > as a type. We now do. Breaking code for one single minor version is > perfectly acceptable, especially given that there are other codebases that > will break if we do not include the question mark. > >