@WG-prioritization/alerts issue #77112 has been requested for prioritization.
agree with @Jonas Schievink here, this shouldn't compile
I wonder what kind of bad things could happen
This seems really bad. I would go with critical but I’m fine with high too
it's not unsound but it seems like the fix would have to be backwards-incompatible
I don't feel like this is
P-critical. I am not even sure if it's
We already have a bunch of similar issues, #66057 as mentioned in the issue itself
and the most relevant one is probably #41756
agree with @lcnr but I do wonder if something bad could happen
anyway to me seems like
If we assign a
P-medium the issue may finish up under the radar for a while. Could it make sense to also mention these other issues as related so we minimize the risk of forgetting it?
looking at that issue, it feels fine to be p-medium to me and go under a radar "a bit"
yeah, I don't expect that we can get unsoundness here
so I don't mind not prioritizing things like this
you mean prioritising it as medium or not prioritising at all?
Prioritizing it as
P-medium is fine, but I don't think we should put a high priority on fixing this
Ok, based on context
P-medium seems the reasonable choice here :thumbs_up: I'll apply the tag.
thanks @lcnr for helping getting more context
Issue #77112's prioritization request has been removed.