Skip to content

Commit 02a5d49

Browse files
authored
Merge pull request #33 from lqd/polonius_meeting
Polonius WG: add minutes for the 2019/03/07 meeting
2 parents cf06649 + eaa9654 commit 02a5d49

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# WG-Polonius meeting minutes: 2019/03/07
2+
---
3+
4+
Relevant links:
5+
- The meeting happened in this [Zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/186049-t-compiler.2Fwg-polonius/topic/meeting.202019.2E03.2E07)
6+
- The [Paper document](https://paper.dropbox.com/doc/Polonius-Roadmap--AY6C806s~AZK~e7wagmys2_wAg-hk3a9ynduUN2gk1A0NNTF) for the WIP roadmap
7+
8+
---
9+
10+
The first meeting of the WG Polonius was dedicated to finding concrete next steps, both as part of working on the roadmap, and as onboarding [@albins][Albin] into the group. Since [Albin] will do a masters related to Polonius, we also worked out other areas they could tackle as time progressed.
11+
12+
Ultimately, a good starter issue was found in creating a new Polonius "hybrid" variant, bridging the location insensitive and complete analyses: a realistic way for rustc to use Polonius.
13+
14+
We then described a possible follow-up task, focusing on Polonius completeness: incorporating rustc's move/overwrite analysis, in a way similar to how it was done in Lark.
15+
16+
We also spent time talking about next steps in documentation, whether in talks ([Niko]) or written docs ([Rémy]).
17+
18+
Possible talks:
19+
- a walkthrough of a more complex theoretical example
20+
- a more practical walk-through with a focus on the concrete parts of the Polonius computation: interfacing with rustc and transferring data, computing the analysis' datalog rules, how datafrog works.
21+
22+
Following those, we also mentioned a longer term task: the more complicated analysis handling higher-ranked regions described in [this blog post](http://smallcultfollowing.com/babysteps/blog/2019/01/21/hereditary-harrop-region-constraints/).
23+
24+
The final points were more about crosscutting concerns applicable to all WGs: how would Github permissions work, and setting up the polonius and datafrog to follow the soon-to-be finalized "crate conformance policy".
25+
26+
----
27+
The major next steps we decided on were:
28+
- [Matthew] will write mentoring instructions for the [hybrid algorithm task](https://github.com/rust-lang/polonius/issues/100)
29+
- [Niko] and [Albin] will prepare the follow-up walkthrough of Polonius (the specific time, and contents).
30+
- [Niko] will review the [subset relation PR](https://github.com/rust-lang/polonius/pull/99)
31+
32+
[Albin]: https://github.com/albins
33+
[Niko]: https://github.com/nikomatsakis
34+
[Matthew]: https://github.com/matthewjasper
35+
[Rémy]: https://github.com/lqd
36+
[Lark]: https://github.com/lark-exploration/lark/blob/master/components/lark-type-check/src/full_inference/analysis/initialization.rs

0 commit comments

Comments
 (0)