"but operator overloading makes your code confusing"
ok bro literally what is this
ok bro literally what is this
"people can misuse it"
oh no what if people make a "GlorbAllNoots()" function that florps all goobers instead??
looks like we can't have functions either, look at this confusing and hidden implicit behavior!!
oh no what if people make a "GlorbAllNoots()" function that florps all goobers instead??
looks like we can't have functions either, look at this confusing and hidden implicit behavior!!
I just don't see how:
vec2.add(vec2.mul(a,1-t),vec2.mul(b,t))
or
a.mul(1-t).add(b.mul(t))
is more readable/better than:
a*(t-1)+b*t
doing math heavy projects without operator overloading is an absolute nightmare
vec2.add(vec2.mul(a,1-t),vec2.mul(b,t))
or
a.mul(1-t).add(b.mul(t))
is more readable/better than:
a*(t-1)+b*t
doing math heavy projects without operator overloading is an absolute nightmare
"what about the cross product that was confusingly defined in this one codebase"
yeah then just don't define operators in ambiguous cases like that? functions still exist, they're not mutually exclusive
the possibility of using a feature in bad ways doesn't make the feature bad
yeah then just don't define operators in ambiguous cases like that? functions still exist, they're not mutually exclusive
the possibility of using a feature in bad ways doesn't make the feature bad
• • •
Missing some Tweet in this thread? You can try to
force a refresh
