Our great sponsors
c2rust | langs | |
---|---|---|
46 | 185 | |
3,631 | 82 | |
2.5% | - | |
9.5 | 9.3 | |
10 days ago | 4 days ago | |
Rust | C | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
c2rust
-
Converting the Kernel to C++
A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123
An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust
It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/
-
Emitting Safer Rust with C2Rust
> The date at the bottom of the article is 2022-06-13. Has there been further progress?
The article links to their github repo:
https://github.com/immunant/c2rust
There's commits in the last hour, so at least some signal of life.
-
Writing an OS in Rust to run on RISC-V
This is arguably already the state of things.
Rust might get compiled down through MIR, down through LLVM IR, down to assembly or wasm... which then might be JIT or AOT (re)compiled into other bytecodes... which might perhaps be decompiled back up to C... and C might be retranslated back to horrific unsafe-spamming Rust by the likes of https://c2rust.com/. We've come full circle!
The main issue is that retranslating high level languages into other high level languages isn't something that there's actually a lot of demand for, especially commercially, especially given the N x M translation matrix going on. So a lot of the projects "stabilize" (get abandoned). And automatically translating between the idioms of those languages gets even nastier in terms of matrix bloat.
Well, you've got stuff like MSIL and JVM bytecodes which are higher level, and preserve more type information, and can be compiled to / decompiled from while still preserving more structure, but they still form competing incompatible ecosystems.
-
Will Carbon Replace C++?
That's the wrong direction. What's needed are intelligent converters which convert less-strict languages to more-strict ones.
Non-intelligent converters just make a mess. Here's c2rust.[1]
Classic C++ to modern C++, plus a compiler flag to lock out all the old unsafe stuff, would be an achievement.
- What would you rewrite in Rust?
-
Red Black Tree in Rust
Well, technically, it's not hard to build such data structures. If you are willing to liberally use raw pointers, UnsafeCell, MaybeUninit and ManuallyDrop, then you can more-or-less write C-equivalent code in unsafe Rust. (there are even transpilers from C to Rust)
-
C2Rust Transpiler
In the chart at [1], this step is represented by a magic wand.
(I wanted to give some examples, but https://c2rust.com/ seems to not be translating today.)
-
Pitchfork: Rack HTTP server for shared-nothing architecture
There are some tools specific to some transformations at least:
-
“Rust is safe” is not some kind of absolute guarantee of code safety
I expect that is because you're not particularly familiar with either LLVM or Rust, considering C can literally be transpiled to Rust.
langs
- How does the compiler know that an already typedefed ident is meant to be a new declarator?
- What makes a language easy for writing a parser?
- Automatic import of C headers —how to deal with macros?
- Register Window in a Stack VM Interpreter
-
A challenge: 52 languages in 52 weeks
Well, I only wrote a few dozen lines in each. (Those benchmarks I wrote are here, all in one file; scroll through to find them. Those two will be at the end.
-
'Switch' and 'Computed Goto'
Next I tried writing a custom C program just for the VM execute function; mostly this was a framework machine-generated from my interpreter, with the handlers necessary filled in manually.
This is my doswitch/u-based test program, a mini-interpreter executing a loop.
-
Is it possible to optimize this bytecode interpreter more?
Actually the next thing I did after trying svm.c was to port it to my systems language to see how my compiler managed with it. (Source is here.)
-
Where are the C Alternatives?
I have taken something away from Forth which is the (a--b) notation that describes the stack behaviour. I use it in these early docs of my IL here.
- Langception IV: I wrote BASIC in Charm, which I also wrote.
What are some alternatives?
prolog-to-minizinc - A Prolog-to-MiniZinc translator
min-sized-rust - 🦀 How to minimize Rust binary size 📦
subsurface - This is the official upstream of the Subsurface divelog program
librope - UTF-8 rope library for C
rakudo - 🦋 Rakudo – Raku on MoarVM, JVM, and JS
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
zz - 🍺🐙 ZetZ a zymbolic verifier and tranzpiler to bare metal C [Moved to: https://github.com/zetzit/zz]
checkedc - Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe. The goal is to let people easily make their existing C code type-safe and eliminate entire classes of errors. Checked C does not address use-after-free errors. This repo has a wiki for Checked C, sample code, the specification, and test code.
vox - Vox language compiler. AOT / JIT / Linker. Zero dependencies
wabt - The WebAssembly Binary Toolkit
rtorrent - rTorrent BitTorrent client
factor - Factor programming language