There's a big difference between creating arbitrary operators like c++, and
just allowing the predefined set of operators to be implemented for custom
types only. The later, combined with the overall aversion of the Go
community towards operator overloading as a whole, will probably lead to
On Sat, Aug 8, 2020 at 5:58 AM 'Carla Pfaff' via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> On Saturday, 8 August 2020 at 01:33:59 UTC+2 Patrick Smith wrote:
>
>> if we think it likely that a future version of Go will allow operator
>> overloading
>>
>
> That's highly unlikely:
On Saturday, 8 August 2020 at 01:33:59 UTC+2 Patrick Smith wrote:
> if we think it likely that a future version of Go will allow operator
> overloading
>
That's highly unlikely: https://golang.org/doc/faq#overloading
--
You received this message because you are subscribed to the Google
