5 ms·

The problem with operator overloading is it makes things confusing when mixing types and let's programmers write confusing code. Person x; Job y; C

The problem with operator overloading is it makes things confusing when mixing types and let's programmers write confusing code. Person x; Job y; CustomType z = x + y; WTF is Z? Is the argument, anyway, I support operator overloading.

xigoi 6mo ago
> WTF is Z? Hopefully a type error, because no sane programmer would implement addition like this. Obviously an insane programmer could, but that’s not the fault of operator overloading. The following code is exactly as confusing: Person x; Job y; CustomType z = add(x, y);
- tpxl 6mo ago
  I don't know; you can bit shift an output stream by a string (or char array) in C++ (std::cout << "Hello, world!"). That seems pretty mad to me.
  - xigoi 6mo ago
    Are you trying to imply that Bjarne Stroustrup is a sane programmer?
bonesss 6mo ago
> WTF is Z? Take a person, add a job, you get an Employee or EmployedPerson. Person.add(job). I agree overloading can create footguns, but domain concepts should make a lot of sense in context when basic arithmetic operations are performed on them. Party = Meeting + Booze. Custom operators are a big assistance for DSLs, and overloading can also aide their creation and elegance. Part of the “awesome but don’t be a jerk about it” toolbox.
joe_mwangi 6mo ago
Java’s planned approach is more like typeclass-style interfaces than unrestricted operator overloading. Types opt into core-defined operator contracts, rather than every library inventing arbitrary meanings for symbols.