Skip to content

Commit 71f4997

Browse files
authored
Merge pull request #35 from lqd/more_polonius
Some more polonius content
2 parents 80f915e + 9c64150 commit 71f4997

File tree

3 files changed

+12
-10
lines changed

3 files changed

+12
-10
lines changed

README.md

+3
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,7 @@ Name | Status | Short
5959
[Profile-Guided Optimization](working-groups/pgo/) | Active | Implementing profile-guided optimization for rustc | [#t-compiler/wg-profile-guided-optimization][pgo_stream]
6060
[MIR Optimizations](working-groups/mir-opt/) | Active | Write MIR optimizations and refactor the MIR to be more optimizable. | [#t-compiler/wg-mir-opt][mir-opt-stream]
6161
[Rustc pipelining](working-groups/pipelining/) | Active | Enable Cargo to invoke rustc in a pipelined fashion, speeding up crate graph compiles. | [#t-compiler/wg-pipelining][pipelining-stream]
62+
[Polonius](working-groups/polonius/) | Active | Exploring the integration of the "NLL 2.0"-like ["Polonius analysis"][Polonius] into rustc | [#t-compiler/wg-polonius][polonius_stream]
6263

6364
[nikomatsakis]: https://github.com/nikomatsakis
6465
[cramertj]: https://github.com/cramertj
@@ -86,6 +87,8 @@ Name | Status | Short
8687
[rfc-2229-stream]: https://rust-lang.zulipchat.com/#narrow/stream/189812-t-compiler.2Fwg-rfc-2229
8788
[mir-opt-stream]: https://rust-lang.zulipchat.com/#narrow/stream/189540-t-compiler.2Fwg-mir-opt
8889
[pipelining-stream]: https://rust-lang.zulipchat.com/#narrow/stream/195180-t-compiler.2Fwg-pipelining
90+
[polonius_stream]: https://rust-lang.zulipchat.com/#narrow/stream/186049-t-compiler.2Fwg-polonius
91+
[Polonius]: https://github.com/rust-lang/polonius
8992

9093
## Expert Map
9194

working-groups/polonius/README.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ one of the goals of the working group is to extend the scope of the
1717
crate to define the full borrow check analysis.
1818

1919
- **Leads:** [@nikomatsakis][nikomatsakis]
20-
- **Meeting Notes:** [All](NOTES.md)
20+
- **Meeting Notes:** [All](minutes/)
2121
- **Screencasts**: [YouTube Playlist](https://www.youtube.com/playlist?list=PL85XCvVPmGQitE2CBzf-gERSqeXo59NQG)
2222

2323
[status]: https://img.shields.io/badge/status-active-brightgreen.svg?style=for-the-badge
@@ -52,9 +52,8 @@ nikomatsakis's blog posts offer the best written documentation at the moment:
5252
## Do I need to attend any meetings?
5353

5454
We have a weekly sync meeting. Check the [compiler team meeting
55-
calendar](../README.md#meeting-calendar) for the most up to date
55+
calendar](../../README.md#meeting-calendar) for the most up to date
5656
time. Attendance is not mandatory but recommended as this can be a
5757
good opportunity to ask any questions and find new issues to work on.
5858

5959
[nikomatsakis]: https://github.com/nikomatsakis
60-
[pnkfelix]: https://github.com/pnkfelix

working-groups/polonius/minutes/2019.03.07-meeting.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -3,31 +3,31 @@
33

44
Relevant links:
55
- 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
6+
- A [Paper document](https://paper.dropbox.com/doc/Polonius-Roadmap--AY6C806s~AZK~e7wagmys2_wAg-hk3a9ynduUN2gk1A0NNTF) for the WIP roadmap
77

88
---
99

1010
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.
1111

1212
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.
1313

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.
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].
1515

1616
We also spent time talking about next steps in documentation, whether in talks ([Niko]) or written docs ([Rémy]).
1717

1818
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.
19+
- a walkthrough of a more complex theoretical example.
20+
- a more practical walkthrough 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, etc.
2121

2222
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/).
2323

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".
24+
The final points were more about cross-cutting concerns applicable to all WGs: how would Github permissions work, and setting up the polonius and datafrog crates and repositories to follow the soon-to-be finalized "crate conformance policy".
2525

2626
----
2727
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)
28+
- [Matthew] will write mentoring instructions for the [hybrid algorithm task](https://github.com/rust-lang/polonius/issues/100).
2929
- [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)
30+
- [Niko] will review the [subset relation PR](https://github.com/rust-lang/polonius/pull/99).
3131

3232
[Albin]: https://github.com/albins
3333
[Niko]: https://github.com/nikomatsakis

0 commit comments

Comments
 (0)