Our great sponsors
console | evcxr | |
---|---|---|
20 | 75 | |
3,095 | 5,131 | |
4.3% | 2.2% | |
8.5 | 8.7 | |
about 23 hours ago | 23 days ago | |
Rust | Rust | |
MIT License | 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.
console
-
Rust Tooling: 8 tools that will increase your productivity
tokio-console is a debugger for Rust async programs that use Tokio. To get started, add the console-subscriber crate to your project and add the following line which will initialise the subscriber and allow tokio-console to connect to it:
-
Using Rust at a startup: A cautionary tale
The tokio-console CLI is a fun one. The console-subscriber supports shipping to a console server running elsewhere, apparently. That gives you a window into what's happening now.
-
Hey Rustaceans! Got a question? Ask here! (42/2022)!
Tokio console maybe? https://github.com/tokio-rs/console
-
Any recommendations for profiling High performance rust code?
I'm building an HTTP load tester called pdc! I have run out of obvious (to me at least) places to look for performance gains. I'm achieving around 45,000 requests per second, per core. Right now I'm using hyper with a separate tokio runtime (in current thread mode) running on each core. So far having runtime on each core/NUMA node has really helped with cache coherency. Any recommendations for profiling beyond tokio console or tokio metrics (Convenient timing amirite!)?
-
Announcing `tracing` 0.1.30 with experimental `valuable`support!
It was just an accident and has been fixed https://github.com/tokio-rs/console/issues/270.
-
[Question] Is Tokio a poor fit for non-network related concurrent applications?
P.S. Tokio [now also has Tokio Console](https://github.com/tokio-rs/console) allowing you to conveniently troubleshoot your tasks if they are causing issues :)
-
Tokio Console
Also, thanks for the thought re: digit precision. I am tracking it here: https://github.com/tokio-rs/console/issues/224
Yes, we've designed the overall architecture of the system to be modular so that the telemetry can be consumed by a number of different UIs --- we'd love to see someone write web interfaces and/or native GUIs for the console data. I have basically no web development experience whatsoever, though, so I went with the terminal app, because not having to learn JavaScript first made it a lot easier to get started :)
We're also thinking about factoring out the Tokio Console command-line application's internal data model and client code into its own library (https://github.com/tokio-rs/console/issues/227) to make it easier to build other UIs on top of that.
-
My heart is making a small jump: Long awaited *cough* tokio-rs/console: a debugger for async rust just released initially!
Issues: https://github.com/tokio-rs/console/issues
I think my issue might have been covered already: https://github.com/tokio-rs/console/issues/179
evcxr
-
Scriptisto: "Shebang interpreter" that enables writing scripts in compiled langs
Emacs didn't invent REPL, and it's common everywhere. For Rust: https://github.com/evcxr/evcxr/blob/main/evcxr_repl/README.m.... But heck, the compiler is reasonably fast enough that any IDE can REPL by compiling the code.
The value here is more in being able to read a script before you run it, then have it run fast, maybe tweaking something here and there. And a compiled script will run 10,000 times faster than LISP, which can be important.
-
Go: What We Got Right, What We Got Wrong
https://github.com/evcxr/evcxr can run Rust in a Jupyter notebook. It's not Golang but close enough.
-
The Hallucinated Rows Incident
The engine uses rust_decimal::Decimal to represent high precision decimal numbers, like the weight property. Serialization of RocksDB keys is done by the storekey crate. To know how Yumi's machine stores diffs, we can now ask- How does storekey serialize rust_decimal? Well, using evcxr to run Rust in Jupyter, the answer is as a null-terminated string:
- TermiC: Terminal C, Interactive C/C++ REPL shell created with BASH
- Exploring Options for Dynamic Code Changes in Rust without Recompilation (hot reloading)
- Go 1.21 will (likely) have a static toolchain on Linux
-
What’s an actual use case for Rust
In theory you should be able to create Rust notebooks (Jupyter notebook) using evcxr so maybe some AI, data analysis, prototyping make sense if you aim for good performance in final application (protype in evcxr and use notebook as reference to implement final application in Rust for speed and safety).
-
would you use rust for scripting?
You should check out evcxr
- Nannou – An open-source creative-coding framework for Rust
-
A Case for Rust in Deep Learning
I think you might like this project: https://github.com/google/evcxr . It brings the REPL workflow to Rust, so having fast iteration should not be an issue.
What are some alternatives?
vscode-jupyter - VS Code Jupyter extension
polars - Dataframes powered by a multithreaded, vectorized query engine, written in Rust
jupyter-rust - a docker container for jupyter notebooks for rust
rust-script - Run Rust files and expressions as scripts without any setup or compilation step.
bincode - A binary encoder / decoder implementation in Rust.
cargo-script - Cargo script subcommand
iron.nvim - Interactive Repl Over Neovim
vim-slime - A vim plugin to give you some slime. (Emacs)
ipython - Official repository for IPython itself. Other repos in the IPython organization contain things like the website, documentation builds, etc.
mirage - MirageOS is a library operating system that constructs unikernels
nsi - High level Rust bindings for Illumination Research’s Nodal Scene Interface – ɴsɪ.
rust-csv - A CSV parser for Rust, with Serde support.