clodboy cowdsire @wallhackio@cat.family

i guess the only interesting thing was how they put the fact that tieflings look like devils in questionable content... like bro, you missed the whole point then you dunce

the pluggedinonline review was not at all interesting, i am very diappointed :(

eggb

apparently if you play as a selune cleric and are romancing shadowheart and gift her the idol of shar she gets angry, thinking it's some sort of trick, and then you get the dialogue option "just take the idol and kiss me like you hate me"

the character generator made mr clean if born a githyanki

what's a good name for a dragonborn bard

which is longer?

surprised there was an ending for karlach that doesn't involve letting her die that actually seems like a happy one

are miniature giant space hamsters actually in dnd lore or is that just a baldur's gate thing

what actually is the preferable alternative to c++, if that is even a good question to ask

kinda funny that raphael got a better boss fight that the true big bad of the game

@Lady younger brother does, in fact, know what a graph is

shadowheart still loves me even though i turned into a worm

what choice did ya'll make after freeing orpheus?

level 12 laezel with haste and cloud strength is so fucking broken lmaooooo

A function call is an lvalue if it returns an lvalue reference meaning the following fucked up and evil code compiles:

int& get_seven() {
  int seven = 7;
  return seven;
}

int main() {
  get_seven() = 8;
}

It's annoying how arbitrary the rules for value categories are.

• casting a value as an rvalue reference is an xvalue since it is an addressable result available to the programmer but the result is also temporary. Ok.

• then casting something as an lvalue reference should be the same, right? Wrong. It is an lvalue because the standard says it is. Ok.

• temporary values, even if they have an address, are still rvalues even if the address is not made available to the programmer (this most often occurs when you return an object from a function call). okay, fine.

• but string literals are lvalues??? & is defined on a string literal? why? why only for string literals and not all objects??????

• accessing an element of an array from an expression for an array that is, itself an rvalue (ie, get_array()[0]) is an xvalue, not a prvalue. I guess, by definition, arrays elements are inherently addressable data available to me so sure, why not.

• but get_object().property is also an xvalue. why. why is it an xvalue. even though objects have addresses they are not exposed to the user if they are temporary so why is the property access now considered addressable??????

I truly don't think it's possible to derive in the general case whether something is a prvalue, xvalue, or lvalue from first principles. For a lot of cases you just have to see what the standard says they are and try to make sense of it.

Maybe if I understood more about compilers there could be good reasons for these value categories but then again, if the language can only be properly understood by understanding implementation details of its compiler then it is not an effective programming language imo.

in a cruel twist of fate, the day after posting about the indomitable work lip gloss, i come in this morning and it has been removed.

this is the first time I have ever mentioned it to anyone. it was a Game, and i lost.