Stream: t-release/triage

Topic: type_length_limit regression


view this post on Zulip lzutao (Aug 30 2020 at 03:51):

Currently there are two opening issues : https://github.com/rust-lang/rust/issues/54540 and https://github.com/rust-lang/rust/issues/64496 .
None of it receives T-compiler attention.
@eddyb said that they want to remove this check in reddit: https://www.reddit.com/r/rust/comments/iingya/compiler_regression_on_1460/g38281x/

Could we nominate the issue and make priority for it ?

view this post on Zulip DPC (Aug 30 2020 at 12:45):

even though we generally don't discuss prioritisation much in this group, thanks for bringing this forward.

view this post on Zulip Léo Lanteri Thauvin (Aug 30 2020 at 13:02):

@lzutao In these cases I think you can use the @rustbot prioritize command on GitHub, eventually with a message explaining why you think the issue should be prioritized. The Prioritization WG can then nominate and prioritize issues as needed

view this post on Zulip DPC (Aug 30 2020 at 13:03):

looking at both issues, one issue seems to be prioritised as P-medium already

view this post on Zulip DPC (Aug 30 2020 at 13:03):

while the other links to it so i guess it sort of inherits that priority

view this post on Zulip DPC (Aug 30 2020 at 13:05):

what we can do in this case (and i've commented on the reddit post as well), is let the user open a new report of the regression they faced, and we can prioritise that and see if we can fix this issue through that :smile:


Last updated: Jan 29 2022 at 10:51 UTC