Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
llvm-project
This fork of the canonical git mirror of the LLVM subversion repository adds (e)Z80 targets. Please refer to the wiki for important build instructions. (by jacobly0)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
There was a recent proposal in Rust for something referred to temporarily as the "interoperable ABI" which may be similar to what you're envisioning. It will define a new calling convention and data representation designed for compatibility with other languages, while supporting some language features not found in C.
Metrics 2, 3, and 7 are faulty, since they inherently favor older languages over newer ones. Take TypeScript vs JavaScript for example. Pretty much everyone and their uncle agrees that TypeScript is superior to JavaScript in every way, yet according to GitHub statistics, JavaScript still beats TypeScript in pull requests, pushes, and starred repositories (source: https://madnight.github.io/githut/).
There's an LLVM fork with Z80 and eZ80 support if you want to start work on that yourself.
Otherwise you could try compiling to C using mrustc and going from there, but as mrustc is really only intended for compiler bootstrapping it won't be a fun experience. Mrustc mostly just assumes that the code you're compiling is valid, so you lose all the advantages of choosing Rust over C in the first place. It also targets x86-64 so the C it emits might need some work before it'll compile.