andrew
banner
andrew-r-thomas.bsky.social
andrew
@andrew-r-thomas.bsky.social
checkersnotchess.dev
Hydrant
November 18, 2025 at 4:25 PM
...
August 26, 2025 at 9:44 PM
Certainly! here's an examp
August 26, 2025 at 9:44 PM
...
August 26, 2025 at 9:44 PM
...
August 26, 2025 at 9:44 PM
June 15, 2025 at 3:51 PM
Yes yes very good
April 23, 2025 at 3:05 AM
Also never type `impl`
April 12, 2025 at 3:51 PM
February 22, 2025 at 3:52 PM
I’m not a language expert though so I’m sure there are some big pieces I’m missing
February 6, 2025 at 11:26 PM
People write sanitizers for catching these issues, but they don’t work that well. It would be great if there were a language that could embed these constraints in the semantics, similar to how rust embeds memory safety constraints. And it would be amazing if there were a language that could do both
February 6, 2025 at 11:26 PM
And it would be nice if there were a systems language that had the capacity to morph to fit these varied needs. For example, I work with a lot of audio systems, and in that world you don’t care as much about memory safety, but you care a lot about realtime safety
February 6, 2025 at 11:26 PM
This makes sense, it may not be possible, but I think what I want is a systems language equivalent of something like lisp (not technically just in spirit). My general intuition is that lower level systems have a lot of breadth and variety in the constraints they care about
February 6, 2025 at 11:26 PM
And in that situation, does it make more sense to build tools that facilitate us building compile time systems (something like zig’s comptime), so that they can be adaptable to our changing understanding of memory safety (and other things)
February 6, 2025 at 7:42 PM
But this makes me wonder how much of borrow checking is fundamental to memory safety, vs how much is it just solving a handful of *known* issues. If it’s leaning toward the latter, what happens when we discover new kinds of memory safety issues
February 6, 2025 at 7:42 PM
Like, it seems that the basic idea around a language being memory safe is: add a system to the language that keeps things memory safe. To me, the big idea, if you can pick only one, of Rust was for this system to be moved from runtime to compile time, that way you dont take a perf hit at runtime
February 6, 2025 at 7:42 PM
On the language side of things, I’m curious what you think about the ability for language memory safety systems to be adaptable for a changing understanding of what makes something “memory safe.”
February 6, 2025 at 7:42 PM
Like maybe on of them is (brightness, hue, contrast etc) another is broad topic like subject and location and action, one of them is emotional context, etc
January 24, 2025 at 1:30 AM
Also, this one I’m a lot less sure about, but you *might* be able to get information about groupings of dimensions that are highly correlated, and have buttons for selecting different, like, “orientation planes” that you could gimbal and scroll your way through
January 24, 2025 at 1:30 AM
I guess you’d lose a lot of the control compared to something like “one slider per dimension” but to me this feels closer to the right way to interact with something like that
January 24, 2025 at 1:23 AM