Live data from Hacker News

Rust panics under the hood, and implementing them in .NET

fractalfir.github.io

1–10 of 83 posts

Re: Rust panics under the hood, and implementing them in .NET

#2
From the repo[0]:

   > The project aims to provide a way to easily use Rust libraries in .NET. It comes with a Rust/.NET interop layer, which allows you to easily interact with .NET code from Rust
Are there some standout Rust libraries out there? Very curious about the motivation and use cases.

[0] https://github.com/FractalFir/rustc_codegen_clr

Re: Rust panics under the hood, and implementing them in .NET

#5

From the repo[0]: > The project aims to provide a way to easily use Rust libraries in .NET. It comes with a Rust/.NET interop layer, which allows you to easily interact with .NET code from Rust Are there some standout Rust libraries out there? Very curious about the motivation and use cases. [0] https://github.com/FractalFir/rustc_codegen_clr

.net considers the rust code "unsafe" so you can do unmanaged, non-GC stuff in the Rust portion of the code.

Re: Rust panics under the hood, and implementing them in .NET

#6

From the repo[0]: > The project aims to provide a way to easily use Rust libraries in .NET. It comes with a Rust/.NET interop layer, which allows you to easily interact with .NET code from Rust Are there some standout Rust libraries out there? Very curious about the motivation and use cases. [0] https://github.com/FractalFir/rustc_codegen_clr

.net considers the rust code "unsafe" so you can do unmanaged, non-GC stuff in the Rust portion of the code.

You can already do that from .NET itself.

My question here is more along the lines of: "what Rust libs are out there that I might be interested in from .NET?"

Re: Rust panics under the hood, and implementing them in .NET

#8

This is really neat, I always wanted to see other languages target .NET much like the JVM was a popular platform to target. Considering .NET is fully MIT licensed I am surprised we dont see more languages that target .NET

That is why CLR used to mean Common Language Runtime, and there were so many languages on the launch event and .NET SDK bundled on computer magazines back in 2001.

Then the Windows only focus (for a while there was Rotor), and Microsoft being Microsoft, all that interest faded away and people focused on the JVM, even though MSIL was designed for all kind of languages (well dynamic came later with Iron languages and DLR), including C and C++.

Nowadays CLR almost feels to have changed into C# Language Runtime, given the C# centric decision on modern .NET design.

Re: Rust panics under the hood, and implementing them in .NET

#9

From the repo[0]: > The project aims to provide a way to easily use Rust libraries in .NET. It comes with a Rust/.NET interop layer, which allows you to easily interact with .NET code from Rust Are there some standout Rust libraries out there? Very curious about the motivation and use cases. [0] https://github.com/FractalFir/rustc_codegen_clr

.net considers the rust code "unsafe" so you can do unmanaged, non-GC stuff in the Rust portion of the code.

In theory, the compiler could do the same as C++/CLI, and output safe Assemblies when specific code patterns aren't used.

Re: Rust panics under the hood, and implementing them in .NET

#10
post #8

This is really neat, I always wanted to see other languages target .NET much like the JVM was a popular platform to target. Considering .NET is fully MIT licensed I am surprised we dont see more languages that target .NET

That is why CLR used to mean Common Language Runtime, and there were so many languages on the launch event and .NET SDK bundled on computer magazines back in 2001. Then the Windows only focus (for a while there was Rotor), and Microsoft being Microsoft, all that interest faded away and people focused on the JVM, even though MSIL was designed for all kind of languages (well dynamic came later with Iron languages and D…

While "C# Language Runtime" as a joke term certainly exists, most runtime improvements benefit all languages that target it, individual changes would have different impact on different languages but that's expected. It is likely further devirt and escape analysis work will have greater impact on F# for example.
Post reply on HN