flowistry
Our great sponsors
rust-foundation-community-grant | flowistry | |
---|---|---|
7 | 15 | |
20 | 1,819 | |
- | - | |
0.0 | 7.3 | |
over 1 year ago | 3 months ago | |
Rust | 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.
rust-foundation-community-grant
-
When do Rust's traits make your life difficult?
That's a topic where already some work exists. You might want to checkout my collection of bad error messages from such trait heavy crates for example. It's important to notice that most of these errors look complicated, but mostly have a quite simple cause. In some of these cases it's even possible to reword these error messages by removing most of the complicated looking type stuff to something much simpler which then is easier to understand.
-
dfdx v0.10.0 - deep learning now with even more const generic goodness
As with everything in static type checking, the upfront costs seem high (deciphering type errors can be a bit daunting for both diesel, and to a certain extent dfdx), but I feel like (1) this will get better (especially with the work /u/weiznich is doing), and (2) history has shown the upfront costs are worth it (as evidenced by the takeover of typescript and typed Python).
-
Diesel 2.0.0 RC1
This change is hopefully only the starting point to a number of future improvements. I've got a project grant as part of the rust foundation community grant program to work on improving the error messages for trait heavy crates like diesel. Hopefully this will result in other improvements as well. I track this work here. If you hit bad error messages with diesel or any other trait heavy crate, please fill an issue there.
-
Survey of bad error messages emitted by the "misuse" of trait heavy crates
axum does basically ]the trick as bevy](https://docs.rs/axum/latest/axum/handler/trait.Handler.html#impl-Handler%3C(T1%2C)%2C%20B%3E) to emulate variadics and someone already filed this https://github.com/weiznich/rust-foundation-community-grant/issues/2
flowistry
- An IDE plugin for Rust that helps you focus on relevant code
- Flowistry: an IDE plugin that analyzes the information flow of Rust programs, showing whether it's possible for one piece of code to affect another
-
Any data flow visualization tools?
https://github.com/willcrichton/flowistry https://github.com/cognitive-engineering-lab/aquascope
-
When do Rust's traits make your life difficult?
Hello Rustaceans, the same lab that has brought you The Rust Book Experiment, Aquascope, and Flowistry is starting a new endeavor. We want to understand when Rust's trait system makes it hard for you to understand or debug a Rust program.
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
I'm personally excited about building developer tools with a sophisticated understanding of your Rust programs. So I've worked on tools like Flowistry and Aquascope.
-
[blog] Rust should own its debugger experience
Maybe this vscode extension could be useful to you?
-
Plugins/extensions for the Rust Analyzer?..
Maybe you would be interested in flowistry?
- flowistry plugin?
-
Learn You an Agda (2014)
Quick, easy formal verification tools that programmers can use on the spot from the IDE are hard to make for most languages because most languages and their compilers weren't made with such thing in mind.
I guess Rust might be heading somewhere interesting with tooling, with tools like Flowistry existing (https://github.com/willcrichton/flowistry) showing what is possible. It's a plugin that can compute backwards / forwards static slices for you, straight in the IDE as a VSCode plugin. I think you need an external program that runs a full program analysis to do the same in C++.
-
Visual lifetime indicator
Based on how Flowistry works I think this should be possible.
What are some alternatives?
metrics
rustviz - Interactively Visualizing Ownership and Borrowing for Rust
uom - Units of measurement -- type-safe zero-cost dimensional analysis
code2flow - Pretty good call graphs for dynamic languages
async-bb8-diesel - Safe asynchronous access to Diesel and the bb8 connection manager
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
diesel - A safe, extensible ORM and Query Builder for Rust
wslgit - Use Git installed in Bash on Windows/Windows Subsystem for Linux (WSL) from Windows and Visual Studio Code (VSCode)
tokio-diesel - Integrate Diesel into Tokio cleanly and efficiently.
dbgee - The zero-configuration debuggee for debuggers. Handy utility that allows you to launch CLI debuggers and VSCode debuggers from the debuggee side.
rust-typed-builder - Compile-time type-checked builder derive
shisho - Lightweight static analyzer for several programming languages