penne
wg-allocators
| penne | wg-allocators | |
|---|---|---|
| 7 | 18 | |
| 42 | 188 | |
| - | 0.0% | |
| 7.3 | 0.0 | |
| 17 days ago | about 3 years ago | |
| Rust | ||
| 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.
penne
-
What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
There are basically two options: - the (Scopes)[http://scopes.rocks] reference logic - the (Penne)[https://github.com/SLiV9/penne] reference logic
-
Introducing: "goto"
I'm not sure if I first read that article before or after starting Penne (https://github.com/SLiV9/penne), but my main motiviation for the language was definitely a response to the ubiquitous "goto considered harmful" mentality, and wanting to see if goto could be redeemed. And for an alt-history language I think Penne makes use of goto pretty well.
-
'#[must_use]' not being the default on functions goes against "Rust has the safest defaults" principle
Excellent suggestion. I've taken my small compiler project, where I don't usually run clippy, and tallied my findings:
-
Which phases/stages does your programming language use?
My Penne compiler has a lexer that turns source code into tokens and a recursive descent parser that produces a list of "common AST" declarations.
-
Do people hand write predictive parsers?
Here's the source code if you're interested: https://github.com/SLiV9/penne/blob/main/src/parser.rs
- Introducing Penne (v0.2.1), a pasta-oriented programming language that favors the goto-statement for flow control
- How to compile my language for LLVM?
wg-allocators
-
Anouncing `stabby` 1.0!
Tracking issue for Storages, and a TLDR on what it is
- What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
-
Custom allocators in Rust
I must have gotten confused, since from your brief discussion with CAD97 it seemed like there was a way for the concepts to live separately and that Storage could complicate things in comparison. But if implementing Allocator in terms of Storage is basically equivalent and Storage is flexible enough that I could write one to pass memory out to unsafe code, that works just as well.
-
Zig and Rust
https://rust-lang.github.io/rfcs/1974-global-allocators.html was the original RFC.
My vague understanding is that there's a working group https://github.com/rust-lang/wg-allocators
The further I get from working on Rust day to day, the less I know about these things, so that's all I've got for you.
-
Rust went from side project to world’s fastest growing language
If you self-reference using pointers and guarantee the struct will never move, you don't even need unsafe. If you self-reference using offsets from the struct's base pointer, you need a splash of unsafe but your struct can be freely moved without invalidating its self-referential "pointers".
Per-struct allocators are a work in progress (see https://github.com/rust-lang/wg-allocators/issues/48).
Not sure what "non thread local addresses" means, but in my experience Rust is pretty good at sending data between threads (without moving it).
- Rust is coming to the Linux kernel
-
FunDSP 0.1.0, an audio processing and synthesis library
Besides that allocation is not really a problem for no_std. It's resolved by using alloc crate directly, so anything usable with custom allocators is supported. Example in dasp sources - https://github.com/RustAudio/dasp/blob/master/dasp_slice/src/boxed.rs#L14-L19 . Also worth looking at this issue to check what is usable already - https://github.com/rust-lang/wg-allocators/issues/7
-
Andrew Kelley claims Zig is faster than Rust in perfomance
But that's on track for rust as well: https://github.com/rust-lang/wg-allocators/issues/7
-
Which important features from C/C++ are missing in Rust
Here: https://github.com/rust-lang/rfcs/pull/1398. there is also a working group for this: https://github.com/rust-lang/wg-allocators.
-
Box<T> allocator override?
It's unstable. wg-allocators contains discussions about design and a tracking issue for collections that need an allocator https://github.com/rust-lang/wg-allocators/issues/7
What are some alternatives?
turbo.fish - ::<> ⠀ https://turbo.fish/ ⠀ <>::
www.ziglang.org
ligmascript - LIGMAScript (the bestest programming language ever) compiler and interpreter
serde-plain - A serde serializer that serializes a subset of types into plain strings
enum-map
rules_rust - Rust rules for Bazel
cryptography - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
dpp - Directly include C headers in D source code
fuzzcheck-rs - Modular, structure-aware, and feedback-driven fuzzing engine for Rust functions
redbpf - Rust library for building and running BPF/eBPF modules
httpdirfs - A filesystem which allows you to mount HTTP directory listings, with a permanent cache. Now with Airsonic / Subsonic support!
reqwest - An easy and powerful Rust HTTP Client