neuronika
futures-rs
neuronika | futures-rs | |
---|---|---|
19 | 11 | |
1,033 | 5,239 | |
1.3% | 0.7% | |
0.0 | 8.4 | |
over 1 year ago | 4 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
neuronika
- This year I tried solving AoC using Rust, here are my impressions coming from Python!
-
Deep Learning in Rust: Burn 0.4.0 released and plans for 2023
Also perhaps comparing to Neuronika.
-
Making a better Tensorflow thanks to strong typing
how does it compare with https://github.com/spearow/juice, https://github.com/neuronika/neuronika and https://github.com/spearow/juice?
-
[D] To what extent can Rust be used for Machine Learning?
Check where and how this struct is used. https://github.com/neuronika/neuronika/blob/variable-rework/neuronika-variable/src/history.rs
-
What do I need for an ML/DL based scripting language in Rust?
Also you can take a look at neuronika.
-
ML in Rust
There is also https://github.com/neuronika/neuronika
-
Enzyme: Towards state-of-the-art AutoDiff in Rust
I have a question: as the maintainer of [neuronika](https://github.com/neuronika/neuronika), a crate that offers dynamic neural network and auto-differentiation with dynamic graphs, I'm looking at a future possible feature for such framework consisting in the possibility of compiling models, getting thus rid of the "dynamic" part, which is not always needed. This would speed the inference and training times quite a bit.
- Any role that Rust could have in the Data world (Big Data, Data Science, Machine learning, etc.)?
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
If you like autograd you will love neuronika
-
bhtsne 0.5.0, now 5.6x faster on a 4 core machine, plus a summary of my Rust journey (so far)
After reading most of the book, I wanted to get my hands dirty. My initial idea was to build a small machine learning framework but I deemed it to be too difficult if not impossible for me at the time. (Now, neuronika would have something to say). When gathering the bibliography for my thesis, I recalled to have stumbled upon a particular algorithm, t-SNE, whom I liked very much. I found the idea behind it to be very clever and elegant (t-SNE it's still one of my favorite algorithms, together with backprop and SOM, I find manifold learning fascinating in general). "So be it", I said, and I began writing a mess of a code, that was basically a translation of the C++ implementation. Boy was it bad.
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
What are some alternatives?
rust-ndarray - ndarray: an N-dimensional array with array views, multidimensional slicing, and efficient operations
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
clblast-rs - clblast bindings for rust
async-std - Async version of the Rust standard library
autograph - Machine Learning Library for Rust
carboxyl - Functional Reactive Programming library for Rust
are-we-learning-yet - How ready is Rust for Machine Learning?
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
justrunmydebugger - just run my debugger. see package here: https://build.opensuse.org/package/show/home:ila.embsys:justrunmydebugger/justrunmydebugger
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
tractjs - Run ONNX and TensorFlow inference in the browser.
coio-rs - Coroutine I/O for Rust