unless it's terminal

fuck I'm lazy

update!!!! Those horrendous 2k are now 140!! Turns out a ton of it was repeated across the codebase, so yours truly properly bagged it all like the errando boy I am oh boy I hate my life

--

the added bonus is I ain't gotta rewrite no test no no, let it buuuuurrrrrrn

update: went there today to get it done with and it seems she's been fired 🤷🏻

by which I mean, what uft8, you think me has such luxuriousness

@Lensflare nope, trouble's been there from inception it's Lua 5.1 & Vim. What can I say, I'm a masochist

@netikras yeah, freebsd FTW

Have an AI to write it and another to grade it. Run both until that resume is written to be unrejectable

@lorentz, I would suggest writing a bigger macro that walks its input, expanding smaller macros inside its input in the way you want. But you'll need this
https://docs.rs/quote/latest/quote or else you'll go insane

@12bitfloat xrist, dude. if a program is syntactically correct and can be typed, the compiler should be able to type it. Peace out ✌🏻

@12bitfloat my own rant to me LMFAO 🤣

@12bitfloat yup, it doesn't want and that's my rant LOL 😆

@12bitfloat To deny that nominal or structural typing influences type inference is like denying the moon landing was filmed on a Hollywood soundstage! Nominal typing is a rigid secret society where your "lineage" (type name) is everything, INFERRING types based solely on their declared name, like a paranoid uncle trusting only birth certificates. Now, structural typing's like a QAnon forum, INFERRING compatibility based on shared "truth" (structure) regardless of names, seeing through disguises like a conspiracy theorist connecting dots between shape-shifters. Whether it's adhering to names or seeing through them, the way types are defined and compared is the secret hand pulling the strings of what your code thinks it knows, making the type system either a deep-state plot or an anarchy of shape-shifters.

@12bitfloat dude, your reasoning makes no sense. We're talking nominal typing, not structural. if a thing's type is X, it is so and that's the end of it. rust-analyzer knows it, I know it, why doesn't rustc? this isn't typescript for fuck sakes

@Wisecrack yup, that's about how clojure wings it. Now, Crystal, oh my, delicious language

@Wisecrack wren looks beautiful and abandoned, just the way I like it

1. painting
2. affection

It's like that everytime. It seems small at first, but it adds up a lot

@kiki like, say, you're doing some async IO. You have coroutines, but you have to write your own async/await mechanism. Same if you're doing OOP, either emulate the "class" keyword or define every single class using prototypical inheritance.

@lorentz aaah yes, forgot one:
coroutine monkey-patching

tco monkey-patching

yeah

basic etiquette, my guys, basic etiquette

Google blinks first for sure

Thou it was called Atom back then

@AlgoRythm it's what they told me 10y ago

@retoor yeaaaah fuck them arrow keys as well, smashing that L never felt so good

@AvatarOfKaine unless you're a degenerate, then I believe every word

nice! But stay the fuck away from any lua code you didn't write. There's shit so horrible you'd go blind just by looking at it

@AvatarOfKaine I did take a break thou deleted my account on the process