☭
And Clodsire doesn't have ears...
@vaporeon_ too fuckin dumb to hear anything
@wallhackio Has a really cool and impressive knowledge of C++, though
(You don't need ears to program in C++)
@vaporeon_ did you see my blog post about rvalues
@wallhackio I did! (Did I forget to favourite it?)
If function names are lvalues, can I assign a function to a different function? Can I say foo = bar; (where foo and bar are functions of the same type) and calling foo() will actually call bar()?
@wallhackio Vaporeon's intuition of lvalues and rvalues is that lvalues can be on the left side on an assignment and rvalues on the right side, but I assume that that doesn't hold up in C++? Does it even hold up in C in all the edge cases?
@vaporeon_ because of const in C++ there are plenty of lvalues which cannot be left of an =
In regards to C, I have no idea, I am not very knowledgeable about C 
@wallhackio @vaporeon_ my intuition is that an lvalue is something that's at least a coherent idea if you try to put it on the left of an assignment. like it doesn't work but there is a well-defined thing that you're trying to do that doesn't work
@monorail @vaporeon_ read my blog
@wallhackio Yeah, right, if I say
const x = 5;, then laterx = 6wouldn't be allowed even ifxis a perfectly fine lvalue...