"I need to keep track of boxed pointers in sret allocas during shadow stack generation" none of these words are in the bible
Alice ✨
@welltypedwit.ch
There’s no sense crying over every mistake. You just keep on trying ’til you run out of cake - GLaDOS
Made a short video showing off a new feature in Waterfall-CAD (my #haskell library for Programmable CAD) www.youtube.com/watch?v=r8tx...
A New Feature in Waterfall-CAD
YouTube video by Joe Warren
youtube.com
I was interviewing someone with 4 years of OCaml experience, and said: "The language solved problems I didn't know I had, but the tooling invented problems I didn't know were possible"
I gave a talk at EMF titled "Men in Tech #YesAllMen", in which I told my experience of being a woman in tech. I was afraid to publish it in case it affected my current or future employment. With all the current news I would like to add my 2¢. So here is the recording: youtu.be/WXL6K1lhvt0?...
Men in tech #YesAllMen - EMF 2026
YouTube video by Electromagnetic Field
youtu.be
I thought that now that i'm writing more rust i could maybe make my peace with method syntax but no. it's so dumb, why are you all doing this to yourselves
%_9.unboxed.sroa.2.i.i.0._9.unboxed.sroa.2.i.i.0._9.unboxed.sroa.2.i.i.0._9.unboxed.sroa.2.i.0._9.unboxed.sroa.2.i.0._9.unboxed.sroa.2.0._9.unboxed.sroa.2.0._9.unboxed.sroa.2.0._9.unboxed.sroa.2.8._10.unboxed.sroa.3.16.copyload.i.i statements dreamed up by the even more deranged (LLVM)
statements dreamed up by the utterly deranged (the vega compiler)
does bluesky just not want me to post right now or is it only about replies
am I overreacting here or is calling your compiler "correct by construction" because you used a newtype and NonEmpty an incredibly dishonest framing? elm-lang.org/news/another...
news/another-step-towards-elm-v1
A delightful language with friendly error messages, great performance, small assets, and no runtime exceptions.
elm-lang.org
it's so strange how like at least 60% of the time when someone makes a claim about "making invalid states unrepresentable", what they actually mean is using a representation with many perfectly representable invalid states that are just hidden behind an abstract type and a smart constructor
it's interesting how every few months half of bluesky gets outraged at the platform's fascist leadership practices (banning people for sending death threats)
you know, i don't love that there is a massive difference between let x = blah(); f(x); g(); and { let x = blah(); f(x); } g(); in rust
i think there is something a little unsatisfying about the explanation that rust's never is not a bottom type and I think it's that it *is* the bottom element of a slightly modified subtyping relation where every type constructor is invariant.
i don't have a blog post yet, but i do have this sketch i drew at 3 am so surely that should clear everything up
- lazy compact regions that use the GC to avoid having to copy anything manually, to maintain sharing for free and that avoid slop (not that kind ^^) because they become regular heap objects instead of needing their own block.
i have so many ideas for vega features that i would really like to implement eventually™ but just haven't had the time for. in no particular order: - bit based layouts: i want layouts to be done on bits instead of bytes so that i can stuff booleans into any unused spaces (e.g. lower pointer bits)
omfg bluesky just deleted like 7 posts because i bumped my mouse against my keyboard and accidentally pressed the back button there is literally a web feature to warn you if you're about to close a tab that contains unsaved work
i just realized that a really cute consequence of the way i would like to re-do layout generation for vega (based on bit sizes rather than byte sizes) is that it's going to give you bitfields for free.
so, what is the intended™ way of doing this in rust? BlockList is an intrusive list of blocks, so it contains lots of pointers and doesn't implement Send. i know what i'm doing though so i *can* get the warning to shut up by making the global mutable (which means that any access is unsafe anyway)
Blog post about instrumenting Lix evaluation with Tracy https://informal.codes/posts/tracy-lix/
I've cut nix eval times in half at work using a new profiling tool I've been playing around with 😎 this is after having picked lots of low hanging fruit in the past
it's genuinely impressive how often the acm pdf reader thing makes every button unclickable i would not know how to do that intentionally without putting in a lot of extra effort
New blog post: "Pining for Arc Downcasting in Rust" https://wolfgirl.dev/blog/2026-09-29-pining-for-arc-downcasting-in-rust/ #programming #rust
funny how if you pick the right benchmark, ghc can beat rustc by a factor of 10