Justin Garcia
@purefunctor
I work on full-stack web and code intelligence, 🇵🇭 he/him
used Amp's Rush 2.0 to write a super basic jj/git status for my starship setup
"However, we wish to stay close to programming practice and define patterns as follows" moscova.inria.fr/~maranget/pa...
Testing out progressive disclosure patterns for compiler testing tools with @ampcode.bsky.social
purescript-analyzer's playground now supports loading PureScript packages from the package set, check it out: purefunctor.github.io/purescript-a...
TIL that Option<NonZero<u32>> has the same size as NonZero<u32> and I'm wondering if it's a worthwhile optimisation to make for flattened ASTs? At 1 billion nodes yeah it'll save 12 GB but at a million 12 MB doesn't matter as much for modern hardware.
The purescript-analyzer currently hovers around 1.0~1.3 GiB of memory usage for 871k (!!!) lines of PureScript. A good chunk of the memory being allocated comes from the AST, specifically the mechanism it currently uses for flattening the representation.
Note to self: make sure the binary you're benchmarking bails if it doesn't find the files it's supposed to be using
I was just thinking about how skolemisation would fit in a constraint-generating type checker and I was wondering if it makes sense to use implication constraints for them.
Why do banks make such terrible software? Like I get hanging on to archaic systems but stuff like this is inexcusable