clodboy @wallhackio@cat.family

@aescling 50% of people are right, 44% of people are wrong, and 6% are cowards

@aescling i dont think there is a "right answer" to that question. all i will say is that, if i designed a compiler, i would treat the case of incorrect code as an expected outcome because i would want to inform the user as clearly as possible what was wrong

@aescling colloquially a compiler can throw. thats fine to say.

@aescling i should clarify that if you didn't put the word "pedantic" in your poll then i would have said yes, but by putting "pedantic" in the cw i responded pedantically

@vaporeon_ very true

@vaporeon_ i haven't checked but the printer i own might be a fax/printer combo

@aescling what the hell is happening here

@aescling @aescling yeah they can but you cant guarantee that a compiler deciding not to compile code is an exception. thats an implementation detail/design choice

@aescling this specific use case does not guarantee that an exception is thrown by the compiler runtime. (it could be how the compiler is chosen to run but who knows? what if the compiler is written in a language without exceptions?) it is a compiler refusing to compile because the code is errant. that is not an exception that is just program behavior

@aescling an error/exception is thrown at runtime. you cant throw an error during compilation its a non-sequitor

@aescling throwing is a runtime concept

I have collected my current understanding of rvalues/lvalues in c++ in the following markdown file:
https://github.com/calebmsword/cpp-notes/blob/main/value%20category.md

@Satsuma @amy i see no downsides to this outcome

@aescling @Satsuma @amy this is a reference to something right

@Satsuma @amy bold to claim that is good taste

@Satsuma @amy reported.

@nsmckinnon oh my god

@amy as a cheesecake enjoyer cheesecake fudge would probably slap tbh.

@amy for some reason my brain instinctively thought that it would taste like chocolate mixed with these flavors and was repulsed for a second