Flowistry: Static Analysis for Understanding Rust Programs

As a part of my Ph.D. research, I've been working on tools to make Rust programs easier to understand. My current project is Flowistry:

Flowistry analyzes the data-flow of a program to answer questions like:

  • What lines of code have no effect on the value of a particular variable?
  • Which lines of code mutate the arguments of the current function?

Please see the README for examples of the extension in action.

Flowistry is still alpha software, so I'm looking for any early adopters that want to try it out! I'd love to know if practicing Rustaceans would find this useful :slight_smile:


This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.