I have to say, the trace-* functionality in Chez Scheme is really growing on me.
(In Scheme it's hard to print-debug. Often you only have a single expression in place and you'd need to add a print with a (begin ...) around it.)
"Alright, this is where the nerd chills start"
Honestly, I didn't know that I needed the term "nerd chills" in my vocabulary but now that I do I'll cherish it forever.
In our book club at @email@example.com we've started reading technical papers. First one: Google's Bigtable paper.
@firstname.lastname@example.org shared this as a companion to the paper: https://read.seas.harvard.edu/~kohler/class/cs261-f11/bigtable.html
It's so good, a perfect match for my style of learning: every explanation starts with "why?"
"gijit: a just-in-time trace-compiled golang interpreter"
That's a Go REPL backed by LuaJIT 🤔
So glad I invested some time into making it easy to write these tests.
Because now it's a ton of fun to add more and find the edge cases.
(btw. how cool is it that I can share daily work like this? open company, woop, woop)
📢 Another Scheme->x86 compiler milestone reached: foreign function calls! ☎
Scheme code can now call C functions. These foreign functions can unwrap the Scheme values and pass Scheme values back.
That was a productive morning!
📢 Just added to Scheme->x86 compiler: separately compiled library of primitives!
These are not built into the compiler, but written in Scheme and will get linked to user code when compiled.
This one was trickier than I thought it would be.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!