sherclod holmes @wallhackio@cat.family

@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

@vaporeon_ @aescling so that operator overloading would Work

@vaporeon_ @aescling this is why they were introduced into the language actually

@vaporeon_ @aescling C++ actually implicitly converts objects to references if the function is declared to take reference arguments

#include <iostream>

class T {};

void use_T(T& t) { std::cout << "I used a T!\n"; }

int main() {
    T t;
    use_T(t);
}

@vaporeon_ @aescling oh you might be right actually.

@vaporeon_ @aescling yes. in C everything is passed by value between functions, so technically the pointer is copied from main to changeObj

but pointers are just numbers so the literal address in memory that pointer refers to doesn't change

@vaporeon_ @aescling there's no optimization in using a reference over a pointer, it's a style thing

@vaporeon_ @aescling they do function as aliases to an existing object but they still pass by value when given to functions, so they can be used in any situation where a pointer can be used because C++ likes giving you multiple ways to solve every problem