@WG-prioritization issue #71471 has been requested for prioritization.
Seems like a
P-low for me
I wonder when this bug appeared
Oh, this nightly, ok
P-low, if someone has a different idea for some reason let us know
Issue #71471's prioritization request has been removed.
I'm doing a quick investigation, but it probably came from my changes to allow more invalid raw strings into the parser level to give better errors.
link to your changes?
@Russell Cohen maybe add the link to your changes in the issue
Actually I'm pretty sure this is from https://github.com/rust-lang/rust/pull/71372/files
@Santiago Pastorino I think we may want to actually prioritize this? It causes things that aren't shebangs (because it's not actually the first line of the file) to be interpreted as a shebang (which then is ignored by the rust compiler). It seems like it _could_ break actual valid code in weird cases although I can't think of anything off the top of my head. It would have to begin with
#! but have a third character that wasn't
[ which is explicitly checked for
yeah, unsure what that may be
I'm inclined to leave this as
P-low but if this breaks something that's actually possible in Rust code yeah we should bump priority for sure
@Russell Cohen anyway, if you're working on a fix it would be great :)
i'd say maybe P-medium?
yeah, to be honest no idea, I haven't looked hard at it but I guess until we don't see real Rust code that this break, it's not really important in my opinion