Crates.io | polonius |
lib.rs | polonius |
version | 0.3.0 |
source | src |
created_at | 2018-05-24 18:16:10.484395 |
updated_at | 2018-12-04 14:50:41.574011 |
description | Core definition for the Rust borrow checker |
homepage | |
repository | https://github.com/rust-lang-nursery/polonius |
max_upload_size | |
id | 66920 |
size | 49,577,420 |
This is a core library that models the borrow check. It implements the analysis described in this blogpost.
The name comes from the famous quote "Neither borrower nor lender be", which comes from the character Polonius in Shakespeare's Hamlet.
One of the goals with this repo is to experiment and compare different
implementations of the same algorithm. You can run the analysis by using cargo run
and you can choose the analysis with -a
. So for example to run against an example
extract from clap, you might do:
> cargo +nightly run --release -- -a DatafrogOpt inputs/clap-rs/app-parser-{{impl}}-add_defaults/
Finished release [optimized] target(s) in 0.05 secs
Running `target/release/borrow-check 'inputs/clap-rs/app-parser-{{impl}}-add_defaults/'`
--------------------------------------------------
Directory: inputs/clap-rs/app-parser-{{impl}}-add_defaults/
Time: 3.856s
You could also try -a Naive
to get the naive rules (more readable,
slower) -- these are the exact rules described in the
blogpost. You can also use -a LocationInsensitive
to use a
location insensitive analysis (faster, but may yield spurious errors).
By default, cargo run
just prints timing. If you also want to see
the results, try --show-tuples
(which will show errors) and maybe
-v
(to show more intermediate computations). You can supply --help
to get more docs.
To run the borrow checker on an input, you first need to generate the
input facts. For that, you will need to run rustc with the
-Znll-facts
option:
> rustc -Znll-facts inputs/issue-47680/issue-47680.rs
Or, for generating the input facts of a crate using the #![feature(nll)]
flag:
> cargo rustc -- -Znll-facts
This will generate a nll-facts
directory with one subdirectory per function:
> ls -F nll-facts
{{impl}}-maybe_next/ main/
You can then run on these directories.