News for hackers. Stuff that matters.

A comment on Why I'm Writing a Scheme Implementation in 2025 (The Answer Is Async Rust).

Re:Why I'm Writing a Scheme Implementation in 2025 (The Answ... by hardwaresofton on Tuesday February 18, 2025 @09:13AM (#43089697)
Glad to see more language runtimes be available from Rust!

Looking forward to scheme-rs being able to benefit from the safety and speed Rust allows

[ Parent | on HN ]
Re:Why I'm Writing a Scheme Implementation in 2025 (The Answ... by dapperdrake on Tuesday February 18, 2025 @12:09PM (#43092207)
It’s about instrumenting Rust’s existing run-time.
[ Parent | on HN ]
Re:Why I'm Writing a Scheme Implementation in 2025 (The Answ... by hardwaresofton on Tuesday February 18, 2025 @12:21PM (#43092383)
Are we reading the same article? It's about this project:

https://crates.io/crates/scheme-rs

[ Parent | on HN ]
Re:Why I'm Writing a Scheme Implementation in 2025 (The Answ... by dapperdrake on Tuesday February 18, 2025 @04:14PM (#43095196)
So? There is instrumentation for Async Rust being added. Just not in the Rust compiler and not in tokio. More in application level code. So as far as the user is concerned to "their" Rust run-time. A distinction that is mostly useless when programming lisp. Hence lisp.

Lisp is about solving your problem and getting the "language" out of the way. So you add what is missing. As long as it works it doesn’t even matter where it’s added.

Even C has a barebones runtime environment when compiled for a machine with an MMU and an OS, so not a microcontroller.

[ Parent | on HN ]