Stream: t-compiler/wg-parallel-rustc

Topic: going forward

nikomatsakis (Jul 05 2019 at 16:45, on Zulip):

Hey @Aaron Turon, @Zoxc, @lwshang and others with an interest in @WG-parallel-rustc :

Should we find a time to discuss status and plans?

Zoxc (Jul 05 2019 at 19:35, on Zulip):

Do we need a sync discussion? I think just merging my PRs and resume existing plans should suffice

cuviper (Jul 05 2019 at 23:55, on Zulip):

"Do we need a sync discussion?" -- that's too meta

cuviper (Jul 05 2019 at 23:55, on Zulip):

if there is a meeting, I'm interested

Aaron Turon (Jul 08 2019 at 17:57, on Zulip):

note: i jotted down some thoughts in the "refcell-vs-lock" thread

nikomatsakis (Jul 08 2019 at 17:59, on Zulip):

Yeah. My update and thoughts:

In the design meeting, we talked about a pre-req being that we address some of the documentation concerns. I had hoped to head that up but of course had no time. But I asked @Aaron Turon to look into it, and gave him an overview of the design plus tips to the various bits of public comments. I'd still like to see more progress on the "design docs" before we go forward -- I think that's important.

nikomatsakis (Jul 08 2019 at 17:59, on Zulip):

(I'll go look at the refcell-vs-lock topic in more detail.)

nikomatsakis (Jul 08 2019 at 18:02, on Zulip):

I'm not sure yet what I think about those concerns. =) I think at minimum I'd like to see a kind of "audit and refactoring list" and a plan for moving forward, but I'm not sure if we need to block on that work being 100% done. The concern of course is that there are very "low probability" bugs that start to appear only once we've released parallel compilation to the public.

I guess at minimum this suggests that we should be sure to do a long enough "opt-in" cycle.

Aaron Turon (Jul 08 2019 at 18:03, on Zulip):

yeah, same -- i think as long as we are steadily working through these concerns and tracking where concurrency issues might arise, we can make improvements in parallel (hah) with the community starting to benefit

Aaron Turon (Jul 08 2019 at 18:03, on Zulip):

re: writing up docs etc, i'd love to go to town on that in the near future -- most likely next week since i'll be traveling to give a conference talk next week

Aaron Turon (Jul 08 2019 at 18:04, on Zulip):

i can start tidying up my review notes this week though, for sure

nikomatsakis (Jul 08 2019 at 18:24, on Zulip):

sounds good to me

Aaron Turon (Aug 16 2019 at 20:30, on Zulip):

hey y'all! i've updated the main tracking issue, and in particular it now links to a sub-tracking issue for the initial shared-state audit. Once the initial audit is complete, I'll work to produce a set of fine-grained issues for areas of shared state to assess, leading to either (1) durable documentation including invariants, atomicity, and lock order, or (2) refactoring to remove the state

Aaron Turon (Aug 16 2019 at 20:32, on Zulip):

those fine-grained issues should be great for splitting up amongst the group if people want to tackle stuff in parallel

Aaron Turon (Aug 16 2019 at 20:33, on Zulip):

once i've got those issues created, i plan to focus on reviewing outstanding PRs for a while

Aaron Turon (Aug 16 2019 at 20:33, on Zulip):

cc @nikomatsakis

nikomatsakis (Aug 17 2019 at 11:16, on Zulip):


Last update: Nov 17 2019 at 07:20UTC