I am interested to see what people say to this. One of the primary reasons I was given by no voters on my operator overload RFC was that it was not useful enough to justify the complexity. Since then however we have had a steady stream of people on list presenting their use cases that have run into issues, and proposing hacks and workarounds.
On Wed, Jun 26, 2024 at 10:25 AM Rob Landers <rob@bottled.codes> wrote: > > - should we revisit operator overloading instead of me hacking my way into > it? > The primary reason I decided not to revisit the RFC with changes or updates was that the conversations I had with voters led me to believe that this was fundamentally unproductive to pursue. I would be happy to bring it again if that changes, but I will not get involved in working on this feature again unless I'm convinced the sentiment of voters has changed, or at least has become changeable. Jordan