News for hackers. Stuff that matters.
Re:A deep dive into Multicore OCaml garbage collector by the_why_of_y on Sunday July 16, 2017 @01:55PM (#14783246)
Haskell doesn't really have the problems that are commonly associated with operator overloading.

Haskell does have type classes, which do allow overloading, even of operators, but the type class uniquely determines the type of the operator - and there can be only one definition of any operator in scope.

Also, you can just define as many new operators as you like.

For these reasons, you can't have the madness of operator<< in C++, or whatever it is that Perl does with the same operator doing 5 completely different things depending on context.

Re:A deep dive into Multicore OCaml garbage collector by tom_mellior on Sunday July 16, 2017 @02:51PM (#14783535)
> Haskell doesn't really have the problems that are commonly associated with operator overloading.

Nobody said it did. People said that it has its own brand of problems with operators looking something like >>+@*<>> peppering your code.

Re:A deep dive into Multicore OCaml garbage collector by ice109 on Sunday July 16, 2017 @06:28PM (#14784439)
lol i wonder if you work on my team
Re:A deep dive into Multicore OCaml garbage collector by ice109 on Sunday July 16, 2017 @06:28PM (#14784435)
>Also, you can just define as many new operators as you like.

this is exactly the problem