On Wed, Sep 2, 2015 at 9:40 AM, Javier Guerra Giraldez
<javier@xxxxxxxxxxx> wrote:
On Wed, Sep 2, 2015 at 11:29 AM, Coda Highland <chighland@xxxxxxxxx> wrote:
excuse me for being dense, but not knowing what's in vogue in C++, i
don't see the connection between object reuse (that i do a lot in
SnabbSwitch) and operator overloading (which i don't use)
Syntactic sugar. Being able to overload = means that you can replace
the normal "leave the current value for the GC to collect, leaving all
other references alone" behavior with "replace the value in the
current object, also modifying all other references."
ah, ok. that's why the proposal included the lhs value as a
parameter, so it's easy to replace assignment with mutation.
i guess i'm in the camp of those that feel that C++ lost much of its
appeal when it became socially acceptable to make innocent-looking
lines of code to have _any_ result and side effect.
not a path that I'd like to see Lua(JIT or not) go
