I'll be taking pre-meeting triage notes regarding NLL in here
there are two A-NLL issues that are otherwise
unprioritized. correction: uncategorized
this doesn't block anything, its just code-cleanup (and is tagged accordingly). Tagging as P-medium.
next: "Simplify handling of feature(bind_by_move_pattern_guards)" #59192
this likewise doesn't block anything. its code-cleanup (and is tagged accordingly). Tagging as P-medium.
oh, those issues were also uncategorized (with respect to NLL-* tags)
they're both kind of internal code cleanliness issues, the existing NLL-* tags do not really apply to them.
I'll change the "Uncategorized" link to filter out things that are tagged C-cleanup
there are seven A-NLL issues that are otherwise unprioritized
first: "confusing error message around trait object bound" #54779
I left some notes. This continues to be not high priority
I'm going to tag it as P-medium
next: "nll: strange suggestion to "consider removing the
a similar case, perhaps even less critical than the previous one if one wanted to try to relate priorities.
next: "NLL diagnostic regression on generator + short-lived yield" #56508
I don't know how to prioritize this one, because I cannot tell if it is going to represent a significant hiccup for people using features like async/await
nominating for discussion at tonight's meeting
&mut &T coerced to
&mut mut x" #57431
this actually looks pretty bad. I'm going to tag it as P-high.
next: "first/second mutable borrow occurs here wrong diagnostic in nll" #57526
I ... am tempted to also tag this as P-high, but it doesn't seem quite as dire as #57431 was
(the heart of the issue is that one might think the compiler is buggy in terms of its claims of first/second, but the reality is that the first+second are correct w.r.t. control-flow. the problem is that its going around a loop, so the source flow is the opposite of the control-flow you need to observe the problem.)
I think I'll leave this untagged for this week. I'll hopefully make up my mind next week about how to prioritize this.
next: "Confusing first/second mutable borrow occurs here diagnostic in NLL" #57528
... this ... looks like a dupe of #57526 ?
last: "issue triage: closures, lifetimes, and nll" #57964
okay so that's all the unprioritized issues. (Some remain unprioritized but I don't mind waiting until next week to finish dealing with them.)
next: Unassigned P-high issues -- there aren't any, yay!
okay. And we have three nominated issues
I just nominated #56508
next: "NLL compile-time performance regression" #58178 ; I had nominated this two weeks ago, but that was to find someone to work on it. @csmoe volunteered after that point. So I'll unnominate.
the last nominated issue is "More restrictive 2 phase borrows - take 2" #58739; the nomination is targeted at the lang team, but as I mentioned on the topic for this PR, I am wondering if we can at least land the PR by changing the lint to default to
but to be honest I think that is unnecessary. Or at least, we can wait until tomorrow; hopefully the lang team will come to consensus then.
(If the lang team fails to reach consensus tomorrow as to what to here, then I will raise the suggestion to default to
and that's all the pre-triage! I'm heading home now, see you all at tonight's meeting.