Sherclod Holmes @wallhackio@cat.family

@cam @cam oh wait i accidentally casted the spell of pee, a common mistake we wizards make. sorry about that. also i am out of mana so youre on your own here

@cam once again i cast the spell of eep upon ye

there is a 95% chance that the most boring piece of shit football game you've ever seen will suddenly get interesting late in the fourth quarter

@The_T @vaporeon_ i guess they both win then!

@The_T @vaporeon_ i think coldsire will be melted by clodfire

@vaporeon_ they both seem very angry, looks like an even fight

@coriander oh that's good

@The_T ⬆️ my genuine reaction to that toot

c++ is such a hack language

oh wait the score is tied im gonna watch again

@vaporeon_ 🫵 vaproeon

@vaporeon_ but its "bad practice" vaproeon i must do it properly by creating a github issue and then assigning myself to it and then making a new branch for work for that issue and then making changes there, and then making a merge request from that new branch :)

@vaporeon_ I actually use git on the command line, even on windows, so whitespace for a filename is annoying for me

not the first time i made things unnecessarily difficult for myself, won't be the last :)

@vaporeon_ there I fixed it :) (by committing directly to the main branch :)))))

@vaporeon_ my bad lmao

@vaporeon_ if you want a real answer then I have my (extremely biased) notes here: https://github.com/calebmsword/cpp-notes/blob/main/value%20category.md

You don't need to read the whole thing to understand lvalues. Just read up to the section titled C++11.

@vaporeon_ in C that was the case because C makes sense. In C++, there are expressions called "lvalue" because C had expressions called "lvalues" and most of them are considered "lvalues" in C++

@vaporeon_ im pretty sure functions cannot be reassigned

in C++ land, where things no longer make sense, there are many lvalues which cannot appear on the left hand side of an assignment

@vaporeon_ in C++, functions names are considered lvalues! I cannot say for certain why this decision was make, I would guess this was probably so that "names of things" could correctly describe lvalues

However, a function name is ambiguous if that function is overloaded, so the & operator throws on the name in that case

@vaporeon_ would you like me to tell you the answer