Rustc_codegen_clr Alternatives

rustc_codegen_clr reviews and mentions

• Rust Is Tier-1 Language at Microsoft
  12 projects | news.ycombinator.com | 10 Sep 2026
• Eurydice: a Rust to C compiler (yes)
  3 projects | news.ycombinator.com | 6 Dec 2025

  Cool.

  One should mention some prior art: https://github.com/FractalFir/rustc_codegen_clr

      rustc_codegen_clr is an experimental Rust compiler backend(plugin), which allows you to transpile Rust into .NET assemblies, or C source files.

• Git: Introduce Rust and announce that it will become mandatorty
  9 projects | news.ycombinator.com | 20 Sep 2025

  Rust has an experimental C backend of its own as part of rustc_codegen_clr https://github.com/FractalFir/rustc_codegen_clr . Would probably work better than trying to transpile C from general LLVM IR.

• Rust to C compiler – 95.9% test pass rate, odd platforms
  8 projects | news.ycombinator.com | 12 Apr 2025

  https://github.com/FractalFir/rustc_codegen_clr - from a quick glance at it, with 1.8k stars and 17 contributors, it deserves a better treatment than a passive—aggressive dismissal like this as a top comment.

  It is a very impressive piece of work.

• A 10x Faster TypeScript
  38 projects | news.ycombinator.com | 11 Mar 2025

  > Cue rust devotees in 3, 2, ..

  If you are a rust devotee, you can use https://github.com/FractalFir/rustc_codegen_clr to compile your rust code to the .NET runtime. The project is still in the works but support is said to be about 95% complete.

• Rust Kernel Policy
  3 projects | news.ycombinator.com | 11 Feb 2025

  We now have https://github.com/FractalFir/rustc_codegen_clr . So we can keep all our Rust files out-of-tree and just submit C code like everyone else.

• Rust-Query
  3 projects | news.ycombinator.com | 30 Nov 2024

  I'm impressed by this individual's effort to bring rust to the clr: https://github.com/FractalFir/rustc_codegen_clr

  It is already way more complete given it's age than I would have expected.

  I agree that the clr is a more natural target than, let's say, the JVM (at least until Project Valhalla comes out).

• Microsoft donates the Mono Project to the Wine team
  30 projects | news.ycombinator.com | 27 Aug 2024

  No, it is not.

  The comparison we discussed was for unrepresentative code that used none of the features that make .NET fast (especially generics, SIMD and devirtualization). The closest case in there was JSON serialization. It is unfortunate that you feel a need to say this, knowing that it doesn't even show a tip of the iceberg.

  Please do not mislead casual readers here with such comments.

  They will have a bad time running basic programs - the original Mono is outdated and cannot execute assemblies that target non-legacy versions, and the Mono that lives in dotnet/runtime (which you have to go out of your way to use on CoreCLR platforms) tends to have all kinds of regressions on user-provided code that is not as robust on runtime checks to ensure that Mono does not accidentally go onto the path that that it has especially bad regression on. Even CoreLib code nowadays uses more and more struct generics assuming monomorhpization which performs poorly on Mono. There is very little work done to improve performance on Mono with effort invested mostly in WASM area and to ensure it does not regress further. Major platforms like Android and iOS are in the slow but steady progress to migrate to CoreCLR/NativeAOT (there are other reasons not in the least much smaller binary size). And for WASM there is NativeAOT-LLVM experiment that is likely to make Mono obsolete for that target too.

  The workloads that matter and are representative are the ones produced by C#, F# and VB.NET compilers as well as projects that care about exercising the standard library and/or produce recommended CIL forms (like https://github.com/FractalFir/rustc_codegen_clr).

• Rust to .NET compiler: Statically Sized, dynamically sized, and other
  1 project | news.ycombinator.com | 6 Jun 2024

  For clarity, that portion after the : is the blog post title, the prefix was added to the submission, so they're kind of disjoint

  One will also want to temper their expectations per https://github.com/FractalFir/rustc_codegen_clr#current-stat... (MIT & Apache 2)

• The search for easier safe systems programming
  11 projects | news.ycombinator.com | 8 May 2024

  I don't have something that could be of Crafting Interpreters level on hand, but the general suggestion given to this question on DotNetEvolution discord by Roslyn team members was to start with the spec itself: https://ecma-international.org/publications-and-standards/st...

  This might be a bit of a learning curve if you don't have experience with writing compilers like that though.

  There are other materials that might prove useful should you go down this path:

  - A series of blog posts of a student who is writing a Rust to .NET compiler which you could follow along: https://fractalfir.github.io/generated_html/home.html The project itself: https://github.com/FractalFir/rustc_codegen_clr

  - A video series on writing a compiler for .NET from scratch: https://www.youtube.com/watch?v=wgHIkdUQbp0&list=PLRAdsfhKI4... Notes: https://github.com/terrajobst/minsk/tree/master/docs

  As for CLR via C#, while it has certain facts that remained the same, the ecosystem has changed a lot since then, you really want to target the latest LTS to get best experience and performance.

  p.s.: if it's any consolation, the promise in CLR via C# of JIT having the advantage of dynamically profiling code execution and compiling to profile-guided version, tuned to the exact hardware and environment is finally fulfilled, many years later :)

• A note from our sponsor - AppSignal
  www.appsignal.com | 12 Sep 2026

  APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product. Learn more →