Stream: t-compiler

Topic: #54818 weekly meeting 2019-01-31


pnkfelix (Jan 31 2019 at 14:30, on Zulip):

Hey @T-compiler/meeting , weekly meeting starting here in about 30min

pnkfelix (Jan 31 2019 at 14:31, on Zulip):

I'm going to try to pre-triage in the meantime.

pnkfelix (Jan 31 2019 at 14:31, on Zulip):

first up: P-high issues

pnkfelix (Jan 31 2019 at 14:32, on Zulip):

first up: "Compiler crash" #57843

pnkfelix (Jan 31 2019 at 14:32, on Zulip):

(i really should have re-titled that a week ago. doing now.)

pnkfelix (Jan 31 2019 at 14:35, on Zulip):

anyway I know this is on @nikomatsakis 's radar now

pnkfelix (Jan 31 2019 at 14:37, on Zulip):

relevant topic thread: https://rust-lang.zulipchat.com/#narrow/stream/144729-wg-traits/topic/.2357843.20universe-related.20ICE

pnkfelix (Jan 31 2019 at 14:37, on Zulip):

so anyway I think we are making progress here. Not sure if its "under control" per se, but there's no much triage to be done

pnkfelix (Jan 31 2019 at 14:38, on Zulip):

next: "ICE on nightly when dereferencing boxed Iterator trait object" #57673

pnkfelix (Jan 31 2019 at 14:38, on Zulip):

this is fixed on nightly. Its still open because its a beta regression

pnkfelix (Jan 31 2019 at 14:39, on Zulip):

there are two distinct PR's that have been posted for fixing it. #57835 is the first step, which already landed and was beta-nominated. I'll beta-nominate @Ariel Ben-Yehuda 's PR #57885 now.

pnkfelix (Jan 31 2019 at 14:39, on Zulip):

(and then we can debate the beta-nominations themselves in the meeting.)

pnkfelix (Jan 31 2019 at 14:41, on Zulip):

(Note that PR #57885 hasn't been r+'ed yet. So it may represent an inherently riskier thing to approve at the moment.)

pnkfelix (Jan 31 2019 at 14:41, on Zulip):

((even though it is superficially a very simple fix.))

pnkfelix (Jan 31 2019 at 14:42, on Zulip):

next: "Regression in trait bounds that are redundant with associated type's HRTB" #57639

pnkfelix (Jan 31 2019 at 14:43, on Zulip):

@nikomatsakis made a comment last week, with

On a shorter time frame, I aim to have some notes and/or experiments here before the next compiler meeting. =)

Any updates here, @nikomatsakis ?

pnkfelix (Jan 31 2019 at 14:44, on Zulip):

next: "[NLL] Bad higher ranked subtype error" #57374

pnkfelix (Jan 31 2019 at 14:45, on Zulip):

the bad diagnostic here is solely exposed via #![feature(nll)], not via the migrate mode we use for 2018 edition.

pnkfelix (Jan 31 2019 at 14:45, on Zulip):

so this is not something that we need to prioritize fixing on the compiler team as a whole.

pnkfelix (Jan 31 2019 at 14:46, on Zulip):

(I've also been poking at it a little today with @lqd )

pnkfelix (Jan 31 2019 at 14:46, on Zulip):

next: " PhantomData fields in repr(C) structs change ABI on aarch64" #56877

pnkfelix (Jan 31 2019 at 14:47, on Zulip):

PR #57645 has merged

nikomatsakis (Jan 31 2019 at 14:47, on Zulip):

first up: "Compiler crash" #57843

if you want, @pnkfelix, you can assign it to me — I wound up getting distracted yesterday by personal stuff and wasn't able to dig into it, but I plan to this week

pnkfelix (Jan 31 2019 at 14:47, on Zulip):

first up: "Compiler crash" #57843

I'll add you to assignee list alongside me

nikomatsakis (Jan 31 2019 at 14:48, on Zulip):

Any updates here, @nikomatsakis ?

No, I failed in my aim. Bah. I'm adding to my calendar a block of time for this tomorrow. (Along with the other PR)

nikomatsakis (Jan 31 2019 at 14:49, on Zulip):

next: " PhantomData fields in repr(C) structs change ABI on aarch64" #56877

Regarding this, I did not close it because there were some questions raised here about whether we got this right. The PR stops the immediate bug, though, and it may be worth either opening a new issue with a fresh history or...I'm not sure.

pnkfelix (Jan 31 2019 at 14:49, on Zulip):

okay I'll leave a note to that effect.

nikomatsakis (Jan 31 2019 at 14:50, on Zulip):

It seems like we are poking at some "poorly understood" areas of the ABI details

nikomatsakis (Jan 31 2019 at 14:50, on Zulip):

Somebody probably needs to do more homework

nikomatsakis (Jan 31 2019 at 14:50, on Zulip):

It's probably not P-high though

pnkfelix (Jan 31 2019 at 14:51, on Zulip):

Hmm okay.

pnkfelix (Jan 31 2019 at 14:52, on Zulip):

next: "prohibit "two-phase borrows" with existing borrows?" #56254

pnkfelix (Jan 31 2019 at 14:53, on Zulip):

this is an NLL issue. I'll add that to the title so that people don't have to look at the tags / interpret words

pnkfelix (Jan 31 2019 at 14:55, on Zulip):

(and I left a note saying that this is waiting for work to finish on @Matthew Jasper 's great PR #57609.)

pnkfelix (Jan 31 2019 at 14:55, on Zulip):

last: "two-phase-borrows need a specification" #46901.

pnkfelix (Jan 31 2019 at 14:55, on Zulip):

I think we'll be talking more about this at the all-hands. I haven't done anything on it really.

nikomatsakis (Jan 31 2019 at 14:56, on Zulip):

I feel like this is probably not P-high but also kind of T-lang

nikomatsakis (Jan 31 2019 at 14:56, on Zulip):

anyway, it's true regardless :)

pnkfelix (Jan 31 2019 at 14:56, on Zulip):

yeah probably.

pnkfelix (Jan 31 2019 at 14:57, on Zulip):

there's a lot of stuff that "needs a specification"

nikomatsakis (Jan 31 2019 at 14:57, on Zulip):

exactly =)

pnkfelix (Jan 31 2019 at 14:57, on Zulip):

let me try to do a preview of the beta-nominations in the 3 minutes remaining before the meeting starts

pnkfelix (Jan 31 2019 at 14:58, on Zulip):

beta-nominations

pnkfelix (Jan 31 2019 at 14:58, on Zulip):

first: "Pass correct arguments to places_conflict" #58008

pnkfelix (Jan 31 2019 at 14:58, on Zulip):

wow

pnkfelix (Jan 31 2019 at 14:59, on Zulip):

well this definitely seems like a low-risk fix...

nikomatsakis (Jan 31 2019 at 14:59, on Zulip):

seems ok

nikomatsakis (Jan 31 2019 at 14:59, on Zulip):

if scary :)

pnkfelix (Jan 31 2019 at 14:59, on Zulip):

I'll put the emojis on the bit above, @nagisa style

nikomatsakis (Jan 31 2019 at 14:59, on Zulip):

(one of those times where I wish Rust had smalltalk or swift-like syntax, with mandatory named arguments)

pnkfelix (Jan 31 2019 at 15:00, on Zulip):

next: "Don't panic when accessing enum variant ctor using Self in match" #58007

pnkfelix (Jan 31 2019 at 15:01, on Zulip):

similarly low risk high reward

pnkfelix (Jan 31 2019 at 15:01, on Zulip):

next: "Fix bug in integer range matching" #57978

pnkfelix (Jan 31 2019 at 15:02, on Zulip):

this change isnt' quite as "trivial" as the others

pnkfelix (Jan 31 2019 at 15:03, on Zulip):

but probably would be clear if one were to read it more carefully than I am at the moment

pnkfelix (Jan 31 2019 at 15:03, on Zulip):

next: "Add information to higher-ranked lifetimes conflicts error messages" #57901

nikomatsakis (Jan 31 2019 at 15:03, on Zulip):

but probably would be clear if one were to read it more carefully than I am at the moment

exactly =) I don't get it, but I trust @varkor does :P

pnkfelix (Jan 31 2019 at 15:04, on Zulip):

There are a lot of commits and files changed in #57901

nikomatsakis (Jan 31 2019 at 15:04, on Zulip):

the actual code changes are relatively few

nikomatsakis (Jan 31 2019 at 15:04, on Zulip):

but not a discrete patch

pnkfelix (Jan 31 2019 at 15:04, on Zulip):

oh yeah I even already said on the PR that I was only nominating it as a matter of following protocol

nikomatsakis (Jan 31 2019 at 15:04, on Zulip):

all localized to the error reporting

nikomatsakis (Jan 31 2019 at 15:04, on Zulip):

and yet still I'm semi-inclined not to backport

nagisa (Jan 31 2019 at 15:04, on Zulip):

#57978 we must backport for it fixes a bug with fairly basic language feature.

nikomatsakis (Jan 31 2019 at 15:04, on Zulip):

I guess it depends how often this comes up, the error is truly bad

pnkfelix (Jan 31 2019 at 15:05, on Zulip):

next: "Avoid committing to autoderef in object method probing" #57885

pnkfelix (Jan 31 2019 at 15:05, on Zulip):

(sorry, I don't mean to cut off discussion)

pnkfelix (Jan 31 2019 at 15:05, on Zulip):

((but I sort of want to get through the whole list quickly... maybe a mistake to try to do this in pre-triage...)))

nagisa (Jan 31 2019 at 15:06, on Zulip):

it is 5 mins past the time meeting began

pnkfelix (Jan 31 2019 at 15:06, on Zulip):

hmm why didn't I see #57835 already in the list

pnkfelix (Jan 31 2019 at 15:06, on Zulip):

@nagisa yeah I know

pnkfelix (Jan 31 2019 at 15:06, on Zulip):

okay maybe I'll stop this and let the meeting itself start

pnkfelix (Jan 31 2019 at 15:06, on Zulip):

Hi @T-compiler/meeting

pnkfelix (Jan 31 2019 at 15:07, on Zulip):

hmm why didn't I see #57835 already in the list

(oh because I'm looking at them in reverse order)

pnkfelix (Jan 31 2019 at 15:08, on Zulip):

so I already went through the P-high issues.

pnkfelix (Jan 31 2019 at 15:08, on Zulip):

I don't think there's anything we need to dwell on there.

pnkfelix (Jan 31 2019 at 15:09, on Zulip):

people can skim over that pre-triage step at their leisure, feel free to chime in with commentary if you like

pnkfelix (Jan 31 2019 at 15:09, on Zulip):

but, under the assumption that that is all well and good, we just need to get through the beta-nominations (full circle!)

pnkfelix (Jan 31 2019 at 15:11, on Zulip):

Summary so far: looks like we will beta-accept PR's #58008, #58007, #57978, #57885

pnkfelix (Jan 31 2019 at 15:12, on Zulip):

and decline PR #57901

pnkfelix (Jan 31 2019 at 15:12, on Zulip):

only beta nomination left for us is: "typeck: remove leaky nested probe during trait object method resolution" #57835

pnkfelix (Jan 31 2019 at 15:12, on Zulip):

which is sort of a pre-req for PR #57885 (which was already mentioned as beta-accept)

pnkfelix (Jan 31 2019 at 15:13, on Zulip):

well, more than sort of.

pnkfelix (Jan 31 2019 at 15:13, on Zulip):

so okay, great. that's all the beta-nominations.

pnkfelix (Jan 31 2019 at 15:14, on Zulip):

there are no stable-nominations for us (that aren't already stable-accepted)

pnkfelix (Jan 31 2019 at 15:14, on Zulip):

next up: stable-to-beta regressions

pnkfelix (Jan 31 2019 at 15:14, on Zulip):

first: "Associated-const ranges in patterns are miscompiled in beta" #57960

pnkfelix (Jan 31 2019 at 15:15, on Zulip):

hmm

pnkfelix (Jan 31 2019 at 15:15, on Zulip):

P-high

pnkfelix (Jan 31 2019 at 15:15, on Zulip):

reporter says they bisected to an NLL PR

pnkfelix (Jan 31 2019 at 15:15, on Zulip):

assigning to self for initial investigation

nikomatsakis (Jan 31 2019 at 15:16, on Zulip):

interesting

nikomatsakis (Jan 31 2019 at 15:16, on Zulip):

cc @davidtwco, #57960 was bisected to #55937

oli (Jan 31 2019 at 15:17, on Zulip):

uh. I should have a look at that, too. I touched constant + pattern code recently

pnkfelix (Jan 31 2019 at 15:18, on Zulip):

its nominated too, but I don't think that's necessary now that's its marked P-high. I'll remove the nomination.

pnkfelix (Jan 31 2019 at 15:18, on Zulip):

next: "Regression in match patterns in beta" #57894

pnkfelix (Jan 31 2019 at 15:19, on Zulip):

has a fix posted in PR #57978

pnkfelix (Jan 31 2019 at 15:20, on Zulip):

(i fixed the description in #57978 so that github understands it fixes #57894 )

pnkfelix (Jan 31 2019 at 15:20, on Zulip):

wait, why did @Pietro Albini remove P-high from #57978 #57894?

pnkfelix (Jan 31 2019 at 15:20, on Zulip):

seems like an accident to me

Pietro Albini (Jan 31 2019 at 15:20, on Zulip):

did I?

Pietro Albini (Jan 31 2019 at 15:21, on Zulip):

oh, that's the PR, I removed P-high on the issue

pnkfelix (Jan 31 2019 at 15:21, on Zulip):

pietroalbini added I-nominated and removed P-high labels 5 days ago

pnkfelix (Jan 31 2019 at 15:21, on Zulip):

we use P-high on issues as our triage mechanism.

Pietro Albini (Jan 31 2019 at 15:22, on Zulip):

the P-high was added by centril, but they intended to add I-nominated

pnkfelix (Jan 31 2019 at 15:22, on Zulip):

ah I see, okay

pnkfelix (Jan 31 2019 at 15:22, on Zulip):

next: "ICE !ty.needs_infer() && !ty.has_placeholders() from boxing closure of type dyn for<'a> _ #57843" (we already discussed this, its already P-high. I just changed the title earlier in meeting.)

pnkfelix (Jan 31 2019 at 15:23, on Zulip):

same for #57673 and #57639: We already triaged them during P-high list

pnkfelix (Jan 31 2019 at 15:23, on Zulip):

that's all the stable-to-beta regressions for T-compiler

pnkfelix (Jan 31 2019 at 15:24, on Zulip):

next, stable-to-nightly regressions

pnkfelix (Jan 31 2019 at 15:24, on Zulip):

first: "Regression from stable to nightly: nested impl trait is not allowed" #57979

pnkfelix (Jan 31 2019 at 15:24, on Zulip):

seems P-high.

pnkfelix (Jan 31 2019 at 15:25, on Zulip):

although as @centril says, this may be a T-lang issue, in terms of deciding if this should ever have been accepted.

pnkfelix (Jan 31 2019 at 15:26, on Zulip):

so is #57979 a T-compiler issue?

nikomatsakis (Jan 31 2019 at 15:26, on Zulip):

I believe I agree with @centril that this was not intended to be accepted.

pnkfelix (Jan 31 2019 at 15:26, on Zulip):

feel free to leave your feelings on the emojis. :)

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

well, I think it's a T-compiler issue, because I think there is no need for t-lang to weigh in

pnkfelix (Jan 31 2019 at 15:27, on Zulip):

ah. heh.

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

I also think it's probably just a "close"

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

presuming we can get away without a warning period :)

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

but I'll leave my comments

pnkfelix (Jan 31 2019 at 15:27, on Zulip):

well E-needstest at very least

pnkfelix (Jan 31 2019 at 15:27, on Zulip):

no?

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

yes :)

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

I'm happy to discuss in lang meeting too

nikomatsakis (Jan 31 2019 at 15:27, on Zulip):

so we can transfer, it's fine

pnkfelix (Jan 31 2019 at 15:28, on Zulip):

next: "Nightly rustc crashes with "unexpected region in query response"" #57464

pnkfelix (Jan 31 2019 at 15:28, on Zulip):

I'll mark as P-high. It was bisected to PR #55517

mw (Jan 31 2019 at 15:29, on Zulip):

that's my favorite PR title yet :)

pnkfelix (Jan 31 2019 at 15:29, on Zulip):

we've looked at all the other T-compiler stable-to-nightly regressions already, as they were tagged as P-high

davidtwco (Jan 31 2019 at 15:30, on Zulip):

cc @davidtwco, #57960 was bisected to #55937

I’ll take a look at this. Sorry, not able to follow the meeting closely today.

pnkfelix (Jan 31 2019 at 15:31, on Zulip):

there's nothing waiting on our team

pnkfelix (Jan 31 2019 at 15:32, on Zulip):

Two issues are tagged I-nominated. One is #57979, which we already discussed (but I'll leave I-nominated since its tagged with T-lang ...)

pnkfelix (Jan 31 2019 at 15:32, on Zulip):

the other is "[do not merge] Measure performance impact of local interners" #57214

pnkfelix (Jan 31 2019 at 15:32, on Zulip):

which we are going to discuss face-to-face next week

pnkfelix (Jan 31 2019 at 15:33, on Zulip):

so that's everything on the "standard" portion of the standing agenda

pnkfelix (Jan 31 2019 at 15:33, on Zulip):

There's, as usual, the slew of unprioritized bugs. But maybe its better to open the meeting up at this point to discuss anything for next weeks' all-hands ahead of time?

pnkfelix (Jan 31 2019 at 15:33, on Zulip):

maybe e.g. tell people what prep they should do?

nikomatsakis (Jan 31 2019 at 15:34, on Zulip):

Sure, that's a good idea

nikomatsakis (Jan 31 2019 at 15:34, on Zulip):

So, I went ahead and "semi-finalized" the schedule, and you can find it at this google spreadsheet.

nikomatsakis (Jan 31 2019 at 15:36, on Zulip):

I wound up going with the following meetings:

nikomatsakis (Jan 31 2019 at 15:36, on Zulip):

Not necessarily everyone wants to add all of those

nikomatsakis (Jan 31 2019 at 15:36, on Zulip):

For each one, there is a DropBox paper document that has an agenda and some notes re: homework etc

nikomatsakis (Jan 31 2019 at 15:36, on Zulip):

Those are not all finalized yet

nikomatsakis (Jan 31 2019 at 15:37, on Zulip):

There are also a number of smaller "breakout" topics that I listed in the "main" Dropbox Paper, here

nikomatsakis (Jan 31 2019 at 15:37, on Zulip):

We don't have a scheduled time to talk about those, but I figured maybe people can talk about them when they don't have other meetings..

mw (Jan 31 2019 at 15:37, on Zulip):

What's "Improvements to incremental synchronization"?

nikomatsakis (Jan 31 2019 at 15:37, on Zulip):

(one thing I had thought about was trying to schedule a time to go over any such things that resulted, but I'm not sure where to fit it in)

nikomatsakis (Jan 31 2019 at 15:37, on Zulip):

@mw I was thinking of those things that you and I talked about at the Mozilla All Hands

nikomatsakis (Jan 31 2019 at 15:38, on Zulip):

that list is really a brainstorm, feel free to remove things

nikomatsakis (Jan 31 2019 at 15:38, on Zulip):

(or add)

nikomatsakis (Jan 31 2019 at 15:38, on Zulip):

I just thought it might be good to try and have some written notes

nagisa (Jan 31 2019 at 15:38, on Zulip):

Does "where to put/how to handle external crates that technically belong to T-compiler" go into the agenda for organizational meeting or should I request for a breakout topic for that?

nikomatsakis (Jan 31 2019 at 15:38, on Zulip):

I imagined that being part of org meeting

nagisa (Jan 31 2019 at 15:38, on Zulip):

great.

mw (Jan 31 2019 at 15:38, on Zulip):

Oh, it should be "Improvements to incremental serialization" then probably

nikomatsakis (Jan 31 2019 at 15:38, on Zulip):

Oh, it should be "Improvements to incremental serialization" then probably

um yes sorry :)

mw (Jan 31 2019 at 15:39, on Zulip):

fixed

nikomatsakis (Jan 31 2019 at 15:39, on Zulip):

One question. I would ideally like to have different "owners" for the various meetings, who can make sure the prep is in place and maybe lead the meeting

nikomatsakis (Jan 31 2019 at 15:39, on Zulip):

Maybe that's not really necessary, but if there's a meeting that is near and dear to your heart, feel free to say so =)

nikomatsakis (Jan 31 2019 at 15:39, on Zulip):

Also, if you think the selections I made should change, that's still a possibility

pnkfelix (Jan 31 2019 at 15:39, on Zulip):

We probably don't want to end up with niko having to own all the meetings

nikomatsakis (Jan 31 2019 at 15:40, on Zulip):

well, for example, @RalfJ willl lead the "validity invariants" meeting

nikomatsakis (Jan 31 2019 at 15:40, on Zulip):

They can maybe say more if they are around, but I think the plan is to kind of review the concept and give some examples of things we rely on validity invariants for

nikomatsakis (Jan 31 2019 at 15:40, on Zulip):

and hopefully get input about other things the compiler is doing today

oli (Jan 31 2019 at 15:40, on Zulip):

I can take the MIR opt mtg

nikomatsakis (Jan 31 2019 at 15:41, on Zulip):

@Oli one thing that would be great for that one is to dig up specific details of things we might want to optimize and why. I added some details about a FF case.

pnkfelix (Jan 31 2019 at 15:41, on Zulip):

the rustc + rustdoc meeting

nikomatsakis (Jan 31 2019 at 15:41, on Zulip):

I'd love it if we can walk out with a plan for doing optimizations X, Y, and Z which we estimate to fix problems A, B, and C

nagisa (Jan 31 2019 at 15:41, on Zulip):

I was thinking about making an introduction for optimisation, but being half deaf I couldn’t possibly lead a live meeting :frown:

pnkfelix (Jan 31 2019 at 15:41, on Zulip):

I would think at least some of us should be at that ("rustc + rustdoc")? Given that rustc appears in title?

oli (Jan 31 2019 at 15:41, on Zulip):

@nagisa we can team up

nikomatsakis (Jan 31 2019 at 15:41, on Zulip):

@nagisa I think if you have thoughts to write up that'd be awesome, somebody else can perhaps talk it out

nikomatsakis (Jan 31 2019 at 15:42, on Zulip):

the rustc + rustdoc meeting

er, yes, sorry

nikomatsakis (Jan 31 2019 at 15:42, on Zulip):

I forgot to list that in my list above

pnkfelix (Jan 31 2019 at 15:42, on Zulip):

are we within edit window? (answer: nope)

nikomatsakis (Jan 31 2019 at 15:43, on Zulip):

I edited it

Zoxc (Jan 31 2019 at 15:43, on Zulip):

@nikomatsakis You can probably add fibers/coroutines to the rustc-rayon topic =P

nikomatsakis (Jan 31 2019 at 15:44, on Zulip):

but also there is a master list in the dropbox paper document

nikomatsakis (Jan 31 2019 at 15:44, on Zulip):

though the times are out of date because @Aaron Turon shuffled some stuff around this morning

nikomatsakis (Jan 31 2019 at 15:44, on Zulip):

@Zoxc given that you are not able to attend, and I'm pretty busy, I'm still not sure how best to manage that meeting. Maybe we can setup something remote. We also could do it outside of the all hands

nikomatsakis (Jan 31 2019 at 15:44, on Zulip):

which might be easier

nikomatsakis (Jan 31 2019 at 15:45, on Zulip):

it'd still be useful to try and do some of the prep work

nikomatsakis (Jan 31 2019 at 15:45, on Zulip):

the main advantage to doing it sooner is that @Josh Stone mentioned they might have interest in doing some rayon hacking etc during all hands

nagisa (Jan 31 2019 at 15:47, on Zulip):

@nagisa I think if you have thoughts to write up that'd be awesome, somebody else can perhaps talk it out

I guess I’ll perhaps give a shot at assembling my ideas into a blog post & failing that I'll link a document somewhere here

nagisa (Jan 31 2019 at 15:48, on Zulip):

failing that I’ll just chat it out with oli during all hands, I’m sure there’ll be time for that over lunch for example.

nikomatsakis (Jan 31 2019 at 15:48, on Zulip):

That would be great; we can link any such thing in the "homework" section =)

nikomatsakis (Jan 31 2019 at 15:49, on Zulip):

which reminds me, there is a lot of great material about the IDE/RLS meeting available

nikomatsakis (Jan 31 2019 at 15:49, on Zulip):

I'll make sure it's all listed, but it'd be great if people are able to consume it pre-meeting

pnkfelix (Jan 31 2019 at 15:55, on Zulip):

okay it looks like that topic is done.

pnkfelix (Jan 31 2019 at 15:56, on Zulip):

Thanks to everyone for attending this weeks meeting! Looking forward to seeing those of you who can come to Berlin next week!

nagisa (Feb 01 2019 at 17:59, on Zulip):

@nikomatsakis @Oli and everyone else, I wrote the blog post

nagisa (Feb 01 2019 at 18:00, on Zulip):

Pardon for the typos, bad grammar, style etc. Timing was somewhat tight compared to what I am usually used to for my blog posts.

mw (Feb 05 2019 at 11:30, on Zulip):

That's an awesome blog post, @nagisa. Thanks!

Zoxc (Feb 19 2019 at 11:55, on Zulip):

I wound up going with the following meetings:

Will there be any summaries from these?

nikomatsakis (Feb 19 2019 at 18:14, on Zulip):

there are notes for all of them, but I'd like to produce some kind of summaries, at least for those I attended. However, been quite occupied. Still, it'd be great to do so, for the people who weren't present

Last update: Nov 16 2019 at 01:50UTC