mustang
verona
mustang | verona | |
---|---|---|
20 | 20 | |
792 | 3,550 | |
- | 0.3% | |
7.5 | 6.6 | |
14 days ago | 13 days ago | |
Rust | C++ | |
GNU General Public License v3.0 or later | MIT License |
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.
mustang
-
OpenBSD 7.5 Released
It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.
Found this as well: https://github.com/sunfishcode/mustang
Some discussion here: https://github.com/bytecodealliance/rustix/issues/76
- Mustang
-
Rust criticism from a Rustacean
On Linux there has been some attempts to get exactly this solutions, most notibly https://github.com/sunfishcode/mustang but the topic did not seem to fetch a prominent position on the supported feature list.
-
Microsoft rewriting core Windows libraries in Rust
For Linux, Mustang already exists because Linux has a stable syscall API
- Mustang: Rust target with std and no linking to a Libc
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
Why bother with a libc at all, when you can skip it entirely on Linux!
-
Why so few, if any, pure Rust apps?
Mustang is a project which is able to run some non-trivial programs written in Rust, such as ripgrep, without using any libc, on Linux.
-
Can rust be entirely written in rust and drop C usage in its code base ?
Mustang is one way to take care of the tiny amount of "C" that runs before main().
-
How do I use Zig as Rust's Standard C Library?
This is more a Rust question than a Zig question. In Rust, the choice of a specific libc (or to not use a libc) is part of the "target", for example many hardware platforms have gnu/musl/none targets. See also relibc or mustang for pure-rust alternatives. Each libc alternative require some work to integrate into Rust.
-
memmapix: A pure Rust library for cross-platform memory mapped IO, which replace libc with rustix.
There's a separate project for that, called Mustang. It's built on top of rustix and provides all those things. It's not super mature yet, but it is able to run ripgrep by itself: https://github.com/sunfishcode/mustang
verona
-
Snmalloc: A Message Passing Allocator
According to this FAQ, snmalloc was designed for the Verona language:
https://microsoft.github.io/verona/faq.html
Unfortunately, I cannot find any significant code samples for Verona on the website or in the GitHub repo. There are a few types defined in a pretty low-level way:
https://github.com/microsoft/verona/tree/master/std/builtin
- Microsoft Project Verona, a research programming language
-
Making C++ Safe Without Borrow Checking, Reference Counting, or Tracing GC
I think the future lies in figuring out how to get the benefits of that secret sauce, while mitigating or avoiding the downsides.
Like Boats said, the borrow checker works really well with data, but not so well with resources. I'd also add that it works well with data transformation, but struggles with abstraction, both the good and bad kind. It works well with tree-shaped data, but struggles with programs where the data has more intra-relationships.
So if we can design some paradigms that can harness Rust's borrow checker's benefits without its drawbacks, that could be pretty stellar. Some promising directions off the top of my head:
* Vale-style "region borrowing" [0] layered on top of a more flexible mutably-aliasing model, either involving single-threaded RC (like in Nim) generational references (like in Vale).
* Forty2 [1] or Verona [2] isolation, which let us choose between arenas and GC for isolated subgraphs. Combining that with some annotations could be a real home run. I think Cone [3] was going in this direction for a while.
* Val's simplified borrowing (mutable value semantics) combined with some form of mutable aliasing (this might sound familiar).
[0] https://verdagon.dev/blog/zero-cost-borrowing-regions-part-1... (am author)
[1] http://forty2.is/
[2] https://github.com/microsoft/verona
[3] https://cone.jondgoodwin.com/
-
A Flexible Type System for Fearless Concurrency
Their approach lines up pretty well with how we do regions in Vale. [0]
Specifically, we consider the "spine" of a linked list to be in a separate "region" than the elements. This lets us freeze the spine, while keeping the elements mutable.
This mechanism is particularly promising because it likely means one can iterate over a collection with zero run-time overhead, without the normal restrictions of a more traditional Rust/Cyclone-like borrow checker. We'll know for sure when we finish part 3 (one-way isolation [1]); part 1 landed in the experimental branch only a few weeks ago.
The main difference between Vale and the paper's approach is that Vale doesn't assume that all elements are self-isolated fields, Vale allows references between elements and even references to the outside world. However, this does mean that Vale sometimes needs "region annotations", whereas the paper's system doesn't need any annotations at all, and that's a real strength of their method.
Other languages are experimenting with regions too, such as Forty2 [2] and Verona [3] though they're leaning more towards a garbage-collection-based approach.
Pretty exciting time for languages!
[0] https://verdagon.dev/blog/zero-cost-borrowing-regions-overvi...
[1] https://verdagon.dev/blog/zero-cost-borrowing-regions-part-3...
[2] http://forty2.is/
[3] https://github.com/microsoft/verona
- Microsoft is rewriting core Windows libraries in Rust
-
Microsoft is to enable Rust use for Windows 11 kernel
Does this count? https://microsoft.github.io/verona/
-
Microsoft rewriting core Windows libraries in Rust
What about new Rust that "Microsoft Research" trying to "explore" https://github.com/microsoft/verona/blob/master/docs/explore.md ?
- Concurrent ownership in Verona
- Concurrent Ownership in Verona
-
Pony Programming Language
Fun fact: the person who created Pony, Sylvan Clebsch, has been working on a Microsoft Research project called Verona. From it's README [0]:
> Project Verona is a research programming language to explore the concept of concurrent ownership. We are providing a new concurrency model that seamlessly integrates ownership.
https://github.com/microsoft/verona/tree/master
What are some alternatives?
ziglibc
tour_of_rust - A tour of rust's language features
relibc - Mirror of https://gitlab.redox-os.org/redox-os/relibc
PurefunctionPipelineDataflow - My Blog: The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with principle-based Warehouse/Workshop Model
liblinux - Linux system calls.
dolt - Dolt – Git for Data
rustix - Safe Rust bindings to POSIX-ish APIs
ante - A safe, easy systems language
jython3 - A sandboxed attempt at v3 (not maintained)
cone - Cone Programming Language
libc - Raw bindings to platform APIs for Rust
felix - The Felix Programming Language