clodboy cowdsire @wallhackio@cat.family

For C++ saying that lvalues are things on which the & operator doesn't throw (and rvalue are things which cause & to throw) is slightly incorrect. After checking the official specification for the language there is a thing called a "qualified-id" that & can operate on, and there is a case where a qualified-id can be a rvalue.

in celebration of world frog day:
https://x.com/blephin_/status/1902179800480882710

oh that's a 60mph wind extreme weather warning for my city tonight. neat.

what if you had a language that passed all variables by value instead of by reference meaning that declarative passing of objects to other functions results in often-expensive copy operations for the arguments to and return value of each function call. so we use pointers for everything. except explicit pointer logic is extremely error prone so instead we should use objects which handle the pointer logic for us. also we need to invent references, which are like pointers but they're different, and add implicit conversion of objects to their references to the 1998 update to the language specification so you can pass these wrapper objects to functions without copies now. but also we need to invent rvalue references so you can pass rvalues to functions as well. btw do you know what an rvalue is? oops wait, these rvalue references so happen to fuck the taxonomy of value categories for the language so now you need to know what an xvalue is teehee

All of this fucking value category bullshit only to realize that the reference operator (&) is valid for lvalues and throws when used on rvalues. This is a valid definition.

i deeply regret to inform that i have started to enjoy the language now that i've learned some things about it.

only a little bit though.

medium joel

on that note, it is a shame that the dark justiciar armor is so badass given that narratively it feels wrong to wear anymore

when the armor is amazing but also is really fucking ugly

the secret to getting jaheira's approval is to call her old apparently

@coriander you should listen to pop out and opi babi from the new carti album, your reaction would be funny

I JUST ROLLED A 1 THREE FUCKING TIMES IN A ROW WHAT THE ACTUAL FUCK

wait you get a permanent status buff for getting a stone statue of yourself in camp lmaooooooo

apparently a lot of people don't like Halsin?

I thought it was quaint when gamers would geek out when experiencing Half-Life 2's physics puzzles for the first time.

And then I stacked three boxes in top of each other in BG3 to reach somewhere I couldn't jump to normally and suddenly I understood

The only Major Criticisms I have so far are

• Shadowheart's arc in Act II, which doesn't feel completely earned. It's a particularly unfortunate thing because her story in the broad strokes should work, but in execution her choices feel flip-floppy instead of conflicted
• The combat, which can be very tedious for too many reasons to contain in a simple bullet point.
• Wyll, for being boring (but he shouldn't! his story has a lot of interesting potential! how is he boring!!! kind of reminds me of Asami from legend of korra, in that the things that happen to him are more interesting than the character itself)

The combat has a lot of great things about it so it's not all bad. But it's the combat which has drained me the most in my playthrough (I probably should not have played on tactician tbh)

I'm deep enough into the game where I feel comfortable saying that the game is excellent (the only way I could dislike it at this point is if we get a Game of Thrones-esque implosion as a conclusion). That being said I do have a lot to critique, although it also doesn't feel fair to do so, given that the game is so massive and mechanically complex that it was destined to have many flaws