futures-rs
mun
futures-rs | mun | |
---|---|---|
11 | 26 | |
5,235 | 1,752 | |
0.6% | 0.9% | |
8.4 | 7.3 | |
about 1 month ago | 17 days ago | |
Rust | Rust | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
futures-rs
-
Which async channel is best?
So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.
-
Async cancellation: a case study of pub-sub in mini-redis
Is this still true after it switched to using FuturesOrdered?
-
I don't really understand how I'm supposed to use async
Done.
-
Confused about how to use tokio to process a vector in parallel
You can use Streams, which are the async version of Iterators; They aren't stable yet, so you'll have to use a crate such as futures.
-
What crates would you consider essential?
futures
-
How to architect Rust code on Async/Await
For traits, like AsyncRead and AsyncWrite, go with the futures crate.
-
Async Rust in Practice: Performance, Pitfalls, Profiling
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551
Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().
That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.
-
Why isn't `rc::Weak<T>` marked `UnwindSafe`when T is `RefUnwindSafe`?
The opposite problem exists as well. Many types are actually unwind safe, but do not get the autotrait. In that case authors would have to manually declare them UnwindSafe. Because this is rarely done, having an API with a trait bound T: UnwindSafe is rarely viable in terms of ergonomics. It now obliges client code to wrap all calls to your API in AssertUnwindSafe which, if they use types from third party libraries, obliges them to assert this is fine. example
-
futures 0.3.9 released with big improvement in compile time
Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this
mun
-
Hotswapping on native languages?
Mun is a statically typed language that compiles to machine code with LLVM, designed to be hot-reloadable: https://mun-lang.org/.
-
Best language to use as a scripting lang for my rust app
Perhaps https://mun-lang.org? Might be a bit raw for your needs tho.
-
Mun v0.4.0 released
But that’s not all! In total, this release contains 111 pull requests made by 5 of our community contributors and our two Core Team members & Dependabot. Thanks for having our back! For a full list have a look at the changelog, but the main improvements are:
-
Mun v0.4.0: a statically-typed scripting language like Rust, written in Rust
Whenever I read about Mun, I'm always really, really intrigued… Until I remember that it currently has no string type and support for one is not currently planned. That's a bit of a shame, IMHO, because otherwise, this looks great!
-
Wren is a small, fast, class-based concurrent scripting language
There's mun [1] which is statically typed and AOT compiled.
1: https://github.com/mun-lang/mun
-
Lessons from Writing a Compiler
From the reverse-dependencies of the salsa crate, the (archived) Lark compiler used it and the Mun compiler uses it.
-
(async) Rust doesn't have to be hard
I notice that there are projects like mun trying to achieve a similar goal, but I'm kind of curious why they are not getting much attention from the community.
-
Rust Is Hard, Or: The Misery of Mainstream Programming
Have you heard of https://mun-lang.org/ ?
It's an embeddable scripting language with the goal of being a Rust-like language that supports hot reloading of functions AND data. To achieve the latter, it uses GC'ed memory such that memory can easily be mapped when the memory's type changes.
It's still in early development but maybe one day will serve your needs :)
-
After working on our Godot + Rust game fulltime for one year it is now up on Steam
In terms of pure Rust engines/frameworks it seems the overall "problem" is lack of scripting, at least from my perspective. Mun seemed extremely interesting, but since even the project itself says "don't use it" I guess it's not a real option, and considering the amount of time we spent on the GDScript/Rust integration I'm a little worried that rolling something more custom would be even less efficient.
- Python interpreter written in rust reaches 10000 commits
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Rhai - Rhai - An embedded scripting language for Rust.
async-std - Async version of the Rust standard library
rune - An embeddable dynamic programming language for Rust.
carboxyl - Functional Reactive Programming library for Rust
janet - A dynamic language and bytecode vm
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
lobster - The Lobster Programming Language
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
RustPython - A Python Interpreter written in Rust
coio-rs - Coroutine I/O for Rust
tl - The compiler for Teal, a typed dialect of Lua