genawaiter
rfcs
Our great sponsors
genawaiter | rfcs | |
---|---|---|
11 | 666 | |
428 | 5,674 | |
- | 0.9% | |
0.0 | 9.7 | |
almost 2 years ago | 7 days ago | |
Rust | Markdown | |
- | Apache License 2.0 |
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.
genawaiter
-
Letlang — Roadblocks and how to overcome them - My programming language targeting Rust
Yes, Letlang is translated to Rust and the runtime is implemented in Rust, using tokio and genawaiter. The compiler itself is also built in Rust.
-
Hey Rustaceans! Got a question? Ask here (7/2023)!
(note that genawaiter itself doesn't support no_std environments, but there's a merge request for that.)
- What is the next big thing coming to Rust
-
A personal list of Rust grievances
> `async` to make fake generators.
Genawaiter[0] is one of them.
-
Generalizing coroutines - The Rust Language Design Team
Are you aware of the genawaiter crate?
-
Do not wait for Rust generators
A warning though: genawaiter doesn't seem to be maintained. The last commit is 2 years old, and issues are not active (I opened one that I find somewhat critical: https://github.com/whatisaphone/genawaiter/issues/35).
-
Hey Rustaceans! Got an easy question? Ask here (46/2021)!
There's e.g. https://github.com/whatisaphone/genawaiter, but you can also use yield directly (https://doc.rust-lang.org/beta/unstable-book/language-features/generators.html).
- What feature would you like to see implemented/stabilized?
- What's the outlook on generator functions in Rust?
-
generators/yield
BTW like was suggested, I have used https://github.com/whatisaphone/genawaiter for my lang and found it pretty easy. Also can be converted into iterator thta make it practical to be part of the iteratos ecosystem:
rfcs
- Coroutines in C
-
Uv: Python Packaging in Rust
Congrats!
> Similarly, uv does not yet generate a platform-agnostic lockfile. This matches pip-tools, but differs from Poetry and PDM, making uv a better fit for projects built around the pip and pip-tools workflows.
Do you expect to make the higher level workflow independent of requirements.txt / support a platform-agnostic lockfile? Being attached to Rye makes me think "no".
Without being platform agnostic, to me this is dead-on-arrival and unable to meet the "Cargo for Python" aim.
> uv supports alternate resolution strategies. By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. But by passing --resolution=lowest, library authors can test their packages against the lowest-compatible version of their dependencies. (This is similar to Go's Minimal version selection.)
> uv allows for resolutions against arbitrary target Python versions. While pip and pip-tools always resolve against the currently-installed Python version (generating, e.g., a Python 3.12-compatible resolution when running under Python 3.12), uv accepts a --python-version parameter, enabling you to generate, e.g., Python 3.7-compatible resolutions even when running under newer versions.
This is great to see though!
I can understand it being a flag on these lower level, directly invoked dependency resolution operations.
While you aren't onto the higher level operations yet, I think it'd be useful to see if there is any cross-ecosystem learning we can do for my MSRV RFC: https://github.com/rust-lang/rfcs/pull/3537
How are you handling pre-releases in you resolution? Unsure how much of that is specified in PEPs. Its something that Cargo is weak in today but we're slowly improving.
- RFC: Rust Has Provenance
-
The bane of my existence: Supporting both async and sync code in Rust
In the early days of Rust there was a debate about whether to support "green threads" and in doing that require runtime support. It was actually implemented and included for a time but it creates problems when trying to do library or embedded code. At the time Go for example chose to go that route, and it was both nice (goroutines are nice to write and well supported) and expensive (effectively requires GC etc). I don't remember the details but there is a Rust RFC from when they removed green threads:
https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...
-
Why stdout is faster than stderr?
I did some more digging. By RFC 899, I believe Alex Crichton meant PR 899 in this repo:
https://github.com/rust-lang/rfcs/pull/899
Still, no real discussion of why unbuffered stderr.
-
Go: What We Got Right, What We Got Wrong
Rust shares Go's "errors as values + panics" philosophy. Rust also has a standard library API for catching panics. Its addition was controversial, but there are two major cases that were specifically enumerated as reasons to add this API: https://github.com/rust-lang/rfcs/blob/master/text/1236-stab...
> It is currently defined as undefined behavior to have a Rust program panic across an FFI boundary. For example if C calls into Rust and Rust panics, then this is undefined behavior. Being able to catch a panic will allow writing C APIs in Rust that do not risk aborting the process they are embedded into.
> Abstractions like thread pools want to catch the panics of tasks being run instead of having the thread torn down (and having to spawn a new thread).
The latter has a few other similar examples, like say, a web server that wants to protect against user code bringing the entire system down.
That said, for various reasons, you don't see catch_unwind used in Rust very often. These are very limited cases.
-
Ask HN: What's the fastest programming language with a large standard library?
Rust has had a stable SIMD vector API[1] for a long time. But, it's architecture specific. The portable API[2] isn't stable yet, but you probably can't use the portable API for some of the more exotic uses of SIMD anyway. Indeed, that's true in .NET's case too[3].
Rust does all this SIMD too. It just isn't in the standard library. But the regex crate does it. Indeed, this is where .NET got its SIMD approach for multiple substring search from in the first place[4]. ;-)
You're right that Rust's standard library is conservatively vectorized though[5]. The main thing blocking this isn't the lack of SIMD availability. It's more about how the standard library is internally structured, and the fact that things like substring search are not actually defined in `std` directly, but rather, in `core`. There are plans to fix this[6].
[1]: https://doc.rust-lang.org/std/arch/index.html
[2]: https://doc.rust-lang.org/std/simd/index.html
[3]: https://github.com/dotnet/runtime/blob/72fae0073b35a404f03c3...
[4]: https://github.com/dotnet/runtime/pull/88394#issuecomment-16...
[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib...
-
Progress toward a GCC-based Rust compiler
Mara's blog post also describes the benefits of standardizing Rust.
Since she created the RFC for standardizing Rust (https://github.com/rust-lang/rfcs/pull/3355) and is also on the team that is working on Rust standardization (https://blog.rust-lang.org/inside-rust/2023/11/15/spec-visio...), I think she was making the point that Rust has good controls in place for adding features while compatibility, not that "Rust does not need a standard".
If she really believed that Rust does not need a standard, why would she create the RFC and join the team working on the effort?
Rust is a great language. There is no reason why it should not have a standard to better formalize its requirements and behaviors.
What are some alternatives?
rust - Empowering everyone to build reliable and efficient software.
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
polonius - Defines the Rust borrow checker.
crates.io - The Rust package registry
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
rust-gc - Simple tracing (mark and sweep) garbage collector for Rust
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
miri - An interpreter for Rust's mid-level intermediate representation
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/