Bumby the Loaf @wallhackio@cat.family

@lapis that one made me giggle uncontrollably when I added it to the poll

Shaft Magus

@vaporeon_ According to the standard, every expression belongs to exactly one of the fundamental classifications lvalue, xvalue, or prvalue.

A prvalue is an expression that 1) when evaluated, initializes an object, or 2) computes the value of an operand of an operator, as specified by the context in which it appears, or 3) has type cv void.

An expression is an xvalue if it is 1) a move-eligible id-expression, 2) the result of calling a function, implicitly or explicitly, whose return type is an rvalue reference to object type, 3) a cast to an rvalue reference to object type, 4) a subscripting operation with an xvalue array operand, 5) a class member access expression designating a non-static data member of non-reference type in which the object expression is an xvalue, or 6) a .* pointer-to-member expression in which the first operand is an xvalue and the second operand is a pointer to data member.

An expression is an lvalue if it satisfies both of the following conditions: 1) it is not an xvalue, and 2) its evaluation determines the identity of an object or function.

I don't think there is a human being on the planet who understands every detail of these definitions.

@The_T @vaporeon_ @amy

@vaporeon_ @amy holy shit she's even smaller now

@vaporeon_ @aescling tell me who hates Go so I can report them

@amy it's the amy!!

@sidd_harth0_5h4h @vaporeon_ what if we comprise and ​ gets a second ice cream with the meal?

@vaporeon_ the default type of inheritance is private inheritance even though no one ever uses it

very well-designed language

@aescling @vaporeon_ From what i've seen I would really like Go

@vaporeon_ no one uses anything other that public inheritance but the other five are there so that you can demonstrate knowledge of language trivia during a job interview

@vaporeon_ you can either inherit something publicly, privately, or protectedly

furthermore, there is virtual or nonvirtual inheritance

so there is private virtual, private, protected virtual, protected, public virtual, and public inheritance

@vaporeon_ did you know that in C++, there are six different ways to inherit a class

@vaporeon_ since that emojo is holding its forehead I am imagining you got a second ice cream and are currently experiencing brain freeze

@monorail @vaporeon_ @aescling it wasn't a reference to anything, you were just there and I felt like saying something nice

@monorail @vaporeon_ @aescling how is that confusing, it is simply an objective fact

@vaporeon_ @aescling I don't like that they don't add anything new, and simply give you a second way to do something the language could already do

I think it is very Bad for languages to do that sort of thing

@cam out of tiredness, or righteous anger? or perhaps both?

@vaporeon_ @aescling using operators in C++ is sugar for a function call, where whatever is given to the operands is provided to the function that represents the operation

of course Bjarne could have decided that pointers of these operands would be provided to the function representing the operations, but that would be too simple. so instead, he added references, and also ruined the language forever