The idea is interesting, but these projects usually fail on semantic mismatch.
Rust’s guarantees (ownership, borrowing, lifetimes) are not just syntax — they’re deeply tied to how the language executes.
If the compiled Go code can’t preserve those guarantees, you risk ending up with something that looks like Rust but behaves like Go, which can be confusing.
Still, as an experiment, it’s a useful way to explore the boundary between language design and compilation targets.
The idea is interesting, but these projects usually fail on semantic mismatch.
Rust’s guarantees (ownership, borrowing, lifetimes) are not just syntax — they’re deeply tied to how the language executes.
If the compiled Go code can’t preserve those guarantees, you risk ending up with something that looks like Rust but behaves like Go, which can be confusing.
Still, as an experiment, it’s a useful way to explore the boundary between language design and compilation targets.
You probably want to post this on Lisette a little language inspired by Rust that compiles to Go (265 points, 146 comments) https://news.ycombinator.com/item?id=47646843