On Tue, Nov 10, 2026 ignace nyamagana butera <[email protected]> wrote:
> > > The interface could be introduced later on, but removing __toString > automatic conversion should be done now. so It may look like a BC break or > a regression vs the current conversion rules but IMHO it would be > beneficial in the long run. I would put the change in the same category as > removing resource to string conversion as you did. > > Hi Ignace, I agree with your reasoning. I've updated the implementation to reject implicit __toString() conversions and published RFC version 1.4 to reflect this. I've also added the dedicated conversion interface to Future Scope. I think it would fit naturally alongside the potential object-oriented API, without expanding the scope of this RFC. Thanks again for the constructive feedback! Best regards, Damian
