elucent

"rep stosw"

when i write 8086 assembly programs I often find myself relying on the REP instruction. i think that makes me a "repper"

who is this quoting lol

an underground explorer and her vehicle come face to face with a ne'er do well

we havent had a president with a valid beta kid name since Bill Clinton. take from that what you will

kamala harris is a valid fantroll name

"if he was on the list, wouldn't the democrats have used that to stop Trump being elected?" is so revealing. i wonder how much of the conspiratorial thinking in the US starts from saying "okay, but the democrats can't actually be *that* incompetent, can they?" and working backwards

like there is nothing functional about jai, and i would argue nothing functional programmers stand to learn from jai, but modern functional programming is often just a crude reactionary movement against writing code with good practices in industry, and in that sense jai fits right in

jonathan blow being platformed at lambdaconf is just the most extreme example of a pattern i've noticed for a while, where a clade of people exists who define "functional programming" as "using one of the Good languages", and every other paradigm is just when you use a Bad language

mfw someone has a bad pl idea

at a certain point of being an ex mc modder and emulation enthusiast i think transitioning becomes less an issue of your own gender identity and more an issue of whether or not you want to support the stereotype

millennials born after 2003 don't even want to play La-Mulana 2 Downloadable Content: The Tower of Oannes anymore. sad!

pixel art of tenna from deltarune chapter 3. one of the mikes is also there and just dropped the pipis

was compelled to draw tenna

it's so funny to me how intense the scala community is. imagine making a reality show about clang libstdc++ maintainers and buying twitter ads for it, and that the reason you would do this is to fight your personal culture war against the gcc libstdc++ maintainers. that's how scala is in real life

oh yeah my take is not that experience is meaningless or anything just that like. when someone is like "heh i'm such an expert i started coding when i was sooooo young" my reaction is more "sorry that happened to you" than "wow that's so impressive"

yeah if anything the fact my work was in front of so many people at an early age was a huge indictment of my emotional maturity, not a flex

i don't actually disagree with this person on any major issues but there's no single thing that more instantly outs you as reputation-obsessed than bringing up "yeah, i coded in high school 😎" years after the fact

and now clover has full support for array/slice patterns too! these even support multiple splat parameters (i.e. rest..., body...) per pattern, which i used to implement this cute BF interpreter :)

added codegen support for swizzling and tuple patterns

metavariable? never hearda variable in my life

on the to-do list:

- implement more types of patterns (list and tuple patterns are planned for now, string patterns later)

- implement &Nil (or maybe just Nil?) to get a pointer to a unitary case, instead of needing a valid instance

- `use List.Cons` and `use List.*` syntax to pull in case defs

whew. had to make a surprising number of backend changes for this, but Clover has sum types and pattern matching now :)

tbh...i think it reads a lot nicer, this looks super crisp

do u think toby fox is catholic or is all that just there by accident

have you considered delta rune

so then the first overall project directory structure aligns with the structure of the import graph

yeah my intent is not enforcing a flat file structure, just also not enforcing a nested one. i think most actual modules would conventionally just put all their sources in one folder, with a `pkg.cl` that defines the module interface and also tells the compiler what other sources to pull in

since these packages would become the minimum compilation unit like in rust, i want them to be especially flexible. like the module system has to support large projects of course. but single-file libraries, projects, and scripts should also be effortless

like i said, `use` would be for importing essentially an analogous type of module to rust crates. the main thing i have qualms about is i want it to require minimal effort to set up - so idk if i want individual sources to have to declare what module they're in, it might be decided from above

my current thinking with clover is splitting imports between `use` (import a, for lack of a better word, crate-level package) and `include` (include another relative source in the current package). simple, more structured than an actual preprocessor, sidesteps needing a Cargo.toml equivalent