4 ms·
Not an interpreter! A compiler :-) Have you seen a stack trace originating from somewhere within tokio? Nearly all useful information is lost. My contention is
by maplant 2y ago
Not an interpreter! A compiler :-)
Have you seen a stack trace originating from somewhere within tokio? Nearly all useful information is lost. My contention is that by isolating the functions that are required to be written in Rust and then doing orchestration, spawning, etc in Scheme the additional debug information at runtime will make the source of errors much more clear.
I could be wrong! But hey there’s other reasons too. Being able to debug Rust functions dynamically is pretty cool, as well as being able to start/stop them like daemons.
- giancarlostoro 2y agoOn the other hand, you might wind up with an impressive Scheme implementation.
- kanbankaren 2y agoluajit gets you almost all of scheme features except macros. Speed of luajit is very close to native C.
- dapperdrake 2y agoSounds like Greenspun's tenth rule.
- kanbankaren 2y agoWell, unlike Lisp & Scheme, Lua and Luajit are used in production, millions of video game consoles, embedded systems, etc.
- UncleEntity 2y agoIsn't this very website written is some sort of lispy goodness?