News for hackers. Stuff that matters.
Re:Redesigning Python's named tuples by smitherfield on Friday September 01, 2017 @01:11AM (#15146263)
> classes have the features of structs (and much more) at the cost of performance.

Not true; C++ classes have zero performance overhead over C/C++ structs (because they're just another word for the same thing).

Of course Python classes have a lot of costly features that C++ classes don't have, but the notion of a "class" (with methods, constructors etc) is not one of them.

Re:Redesigning Python's named tuples by kronos29296 on Friday September 01, 2017 @01:41AM (#15146398)
And also makes them look more complicated with more syntax. C++ has all those features that I will never know without adding performance. But people don't use Python for performance but ease of use.

In C++ ease of use is given up for the sake of performance. In python it is the other way.

Re:Redesigning Python's named tuples by hasenj on Friday September 01, 2017 @04:36AM (#15146998)
Don't C++ classes (and therefore structs) have a hidden vtable?
Re:Redesigning Python's named tuples by plq on Friday September 01, 2017 @04:57AM (#15147076)
vtable is always "hidden". It's only there when there is at least one virtual member defined. Sole difference between class and struct in C++ is default visibility.

    class A {
        int a; // private
    }

    struct A {
        int a; // public
    }
Re:Redesigning Python's named tuples by taejo on Friday September 01, 2017 @04:52AM (#15147053)
Only if they have virtual members.