@WG-prioritization/alerts issue #76785 has been requested for prioritization.
I-nominated
?issues like this have been coming up a lot lately, maybe they should be combined into one?
seperate issues are fine imo, sometimes they get solved at different times
unless it is an exact duplicate
Would this end up being something like a P-Medium since it's a stable to stable regression but has a workaround?
I think I misunderstood the issue, it's a diagnostics regression
and it has a fix that's almost ready too
so I'd go with P-low maybe? since it's a diagnostic regression
I don't understand.
How is this a diagnostic regression?
the bug is not that the limit decreased, but that it doesn't show why the limit decreased
Ah I see, that makes sense.
or maybe it should count as tracking both :shrug: but in that case there are other issues it duplicates
Well I believe that the compiler team (e.g. the reviewer of the culprit of the regression) could decide whether it is right to have a lowered limit
this one is pending prioritization
I'd be fine with P-low
or P-medium
whatever to be honest
saw that @Joshua Nelson thinks P-low
, should we go with it then? or others have different opinion
does it impact code that's an touching a pretty edge case, if I am correct?
I still think this is two separate issues
so we should decide which bit we're prioritizing: the diagnostic problem, which is not a regression, or the type length limit regression
apiraino said:
does it impact code that's an touching a pretty edge case, if I am correct?
not really, there are a lot of recent type length limit issues
interesting :thinking:
@Joshua Nelson can you comment on the issue what you're saying
if they are 2 issues in one, I'd give the priority of the highest one :)
sure
let me read the issue better :)
I guess they are talking about the limit thing and not exactly about the diagnostic
done
ok, I'd go with P-medium
in this case
well whatever :P, I'd agree with the first one that says something that is P-low or P-medium and would leave it up to them to tag it properly
issue has been closed as dupe of #75992