@WG-prioritization/alerts issue #80899 has been requested for prioritization.
This behavior seems very weird. I figured I would prioritize to see if it's a bug or not?
just read #61956 a bit, we don't have to prioritize it and can even close as duplicate, I think?
that issue is unfortunate, intentional and will be fixed either by project safe transmute or const evaluatable bounds
yeah, closing as duplicate seems fine to me
Issue #80899's prioritization request has been removed.