Stream: t-compiler/wg-meta

Topic: closure path capture WG


nikomatsakis (Feb 28 2019 at 16:14, on Zulip):

Hey @blitzerr -- I was thinking we should make a WG related to the closure work you've been doing. And that we should schedule a meeting (maybe tomorrow, if that works for you? Maybe better next week?) to lay out a plan and get things going again, presuming you still want to be push this over the finish line.

blitzerr (Feb 28 2019 at 16:18, on Zulip):

@nikomatsakis
Sure. That works. What time were you thinking for meeting ?

blitzerr (Feb 28 2019 at 16:18, on Zulip):

I do want to see it through release and keep working on it to get there

nikomatsakis (Feb 28 2019 at 16:30, on Zulip):

@blitzerr I didn't have a specific time in mind yet but I'm flexible

nikomatsakis (Feb 28 2019 at 16:30, on Zulip):

Can I list you as a "leader" =)

nikomatsakis (Feb 28 2019 at 16:31, on Zulip):

(As I wrote in a few other places, I think this would probably be the sort of WG where we aren't necessarily trying really hard to recruit a bunch of folks, though it might be cool if we could find 1 or 2 other people for you to work with, as it's often more fun on a team)

blitzerr (Feb 28 2019 at 16:54, on Zulip):

"leader" sounds fancy :joy:

blitzerr (Feb 28 2019 at 16:55, on Zulip):

@nikomatsakis I will create the relevant documents for the closure wg

nikomatsakis (Feb 28 2019 at 16:57, on Zulip):

@blitzerr thanks! Let me know what times would work for you re: a meeting. Maybe Monday at 13:00 East Coast time?

nikomatsakis (Feb 28 2019 at 16:57, on Zulip):

Also, let's come up with a better name

nikomatsakis (Feb 28 2019 at 16:57, on Zulip):

well, whatever the RFC was called

nikomatsakis (Feb 28 2019 at 16:57, on Zulip):

just not 'closure wg' ;)

blitzerr (Feb 28 2019 at 17:00, on Zulip):

@nikomatsakis I am on a different time zone roughly 12 hours. So maybe a before lunch time for you might work for me better. :grinning:

nikomatsakis (Feb 28 2019 at 18:20, on Zulip):

@blitzerr oh, nice, ok

blitzerr (Feb 28 2019 at 18:27, on Zulip):

@nikomatsakis Anytime between 8:30 AM - 11:30 AM your time works for me. I will be in this timezone for the next three weeks.

nikomatsakis (Feb 28 2019 at 18:31, on Zulip):

@blitzerr that's actually surprisingly hard for me next week for some reason. I could probably do Tuesday at 8:30-9:00 my time.

nikomatsakis (Feb 28 2019 at 18:31, on Zulip):

@blitzerr I can send you an invite, this same e-mail?

nikomatsakis (Feb 28 2019 at 18:31, on Zulip):

It might be like 8:45 basically :)

blitzerr (Feb 28 2019 at 18:34, on Zulip):

The email hasn't changed, just the timezone :grinning: Visiting family for a bit here.

nikomatsakis (Feb 28 2019 at 18:36, on Zulip):

I meant "same one you used for Zulip" but sure :)

nikomatsakis (Feb 28 2019 at 18:41, on Zulip):

So the RFC was RFC 2229 - "capture disjoint fields" . Maybe we should call the WG after the RFC?

Some thoughts:

blitzerr (Mar 01 2019 at 04:49, on Zulip):

@nikomatsakis wg-disjoint-field-capture gives some idea but I guess that people can't figure out what it is just by looking at the name of the working group. That makes me lean towards wg-rfc-2229 but then again no one can figure out anything without looking at the RFC. brings us to two hard problems in CS - naming and cache invalidation :D

nikomatsakis (Mar 04 2019 at 20:55, on Zulip):

@blitzerr do you think you can make a PR to the compiler-team repo with the WG definition btw?

nikomatsakis (Mar 04 2019 at 20:55, on Zulip):

Let's do wg-rfc-2229 I guess for now

nikomatsakis (Mar 04 2019 at 20:56, on Zulip):

it's short and at least kind of obvious how to look it up

nikomatsakis (Mar 04 2019 at 20:56, on Zulip):

eh I don't know :) I can't decide

blitzerr (Mar 05 2019 at 02:33, on Zulip):

blitzerr do you think you can make a PR to the compiler-team repo with the WG definition btw?

@nikomatsakis I created one. https://github.com/rust-lang/compiler-team/pull/27
Do you want to review or should I merge ?

blitzerr (Mar 05 2019 at 02:38, on Zulip):

One more thing :
for this wg, do we want to create a new stream or we want to keep using
https://rust-lang.zulipchat.com/#narrow/stream/122657-t-compiler.2Fwg-nll/topic/.2353488.20closure.20and.20disjoint.20fields ?

blitzerr (Mar 05 2019 at 02:53, on Zulip):

Another thing is I also added you as the lead but can remove if you don't want to be one on paper and just want to be the grand mentor for the wg :smiley:

nikomatsakis (Mar 05 2019 at 13:37, on Zulip):

@blitzerr we'll make a new stream

nikomatsakis (Mar 05 2019 at 13:37, on Zulip):

thanks!

nikomatsakis (Mar 05 2019 at 13:37, on Zulip):

let me review quickly

nikomatsakis (Mar 05 2019 at 13:38, on Zulip):

re: lead, I figured i'd be down as lead, but I am hoping we can maybe get a bit of collaboration happening, vs you having to do everything

blitzerr (Mar 05 2019 at 13:41, on Zulip):

Makes sense

nikomatsakis (Mar 05 2019 at 13:43, on Zulip):

https://github.com/rust-lang/compiler-team/pull/27#pullrequestreview-210683189

nikomatsakis (Mar 05 2019 at 14:48, on Zulip):

@blitzerr if you're able to make those edits, I'll merge -- maybe we want to add a link to the paper document, too

blitzerr (Mar 05 2019 at 15:09, on Zulip):

@nikomatsakis I was just thinking about that.
I will link it in the README as the roadmap

blitzerr (Mar 05 2019 at 15:15, on Zulip):

@nikomatsakis
Which big table are you talking here ?
Can you also edit the dreaded "big table" in the main README.md?

blitzerr (Mar 05 2019 at 15:18, on Zulip):

I guess you mean this ?

blitzerr (Mar 05 2019 at 16:00, on Zulip):

@nikomatsakis I addressed your suggestions and merged the changes.

Last update: Nov 18 2019 at 00:40UTC