Hi, I'm new here. Can I chime in on tomorrows meeting?
Absolutely! Anyone interested is welcome to attend!
I see there is Zoom info on the compiler team calendar but I'm not sure if it's accurate (we had issues with it last time).
@pnkfelix Do you know if the compiler team calendar is correct?
(There is a link pnkfelix sent last week.)
I'll go ahead and include what's on the calendar in case that's useful:
Join Zoom Meeting
Meeting ID: 915 4412 8512
Yeah I need to look into that. We have our meeting tomorrow
That info looks right according to my Zoom app
Okay it appears I have the credentials to start that meeting, so it should work for us tomorrow
i might not make it for tomorrow - haven't worked much on the issue assigned to me will get back to it once i'm done with some pr work :grinning:
I will watch the videos afterwards :laughing:
Meeting should be just now, right? @wg-incr-comp
I think so, I'm "waiting for host" on zoom
I have a Zoom lizence. Should I start a meeting instead?
Nevermind, the meeting started ^^
I mentioned on the call that I was writing up a comment before approving @Santiago Pastorino's PR. Well that comment turned into a small document as I dug into the data. I'd appreciate it if a few others could take a look and see if the analysis makes sense and if you agree with my conclusions. Thanks!
@Wesley Wiser makes sense to me
@Wesley Wiser regarding the parts of the hackmd labelled "CGU Issue 1" and "CGU Issue 2": are there actual github issues filed for each of these problems? That is, I assume these are things we should track at the very least; and if we actually think we might be able to address them, then it would be helpful to have github issues if only to serve as "global" unique identifiers for them?
Yeah, that's a great idea. I'm not aware of any existing issues tracking that so I can create some.
"Issue" is perhaps too strong a word. It's more that the existing behavior is suboptimal in certain cases. Regardless, we use issues to track other enhancements so that seems fine to me.
btw does #76896 needs a
@bors retry or what's going on?
it's not spurious though
a little overdue: https://youtu.be/aw629QKeSjQ
Last updated: Oct 21 2021 at 21:02 UTC