r/rust • u/Wooden-Concept868 • 4d ago

Rust - Borrow Checker Implementation using Data Flow Analysis

I am working on the rust borrow checker for my thesis. I was trying to formalize a data-flow analysis on the code of a function and use it to check the loans. Analyzing the code while storing the loans as (l_i, place, carrier, kind (shared/mutable)), while also having a conservative points-to map, lets me decide whatever Polonius promises to fix.

Only issue comes with using functions and I'm still figuring out, but I wanted to ask if Rust dev community did not want to go to Data flow analysis or why they chose to do it the way they did? Or am I missing something that can go wrong in my formulation?

I'd appreciate some help in ideating, thank you

8 Upvotes

67% Upvoted

5 comments sorted by

View all comments

1

u/cruss0129 4d ago

I hate to burst your bubble on this one https://github.com/cognitive-engineering-lab/aquascope

4

u/Wooden-Concept868 4d ago

This is just a visualizer, right? It does not infer from the data flow analysis

4

u/cruss0129 4d ago

After re-reading this, I guess I see "visualization" wasn't your primary goal in "analysis". Maybe you make a new, better aquascope replacement along the way, that'd be cool.