-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[regression] empty shebang parsing #73250
Comments
I personally suspect that we may want to ask T-lang if we're good accepting this as expected breakage. Alternatively I guess we can adjust the shebang detection to not require a non-empty shebang. |
Assigning |
For reference, here's the code responsible for parsing shebang in Linux kernel - https://github.com/torvalds/linux/blob/master/fs/binfmt_script.c (Fully whitespace (including empty) |
I am inclined to close as won't fix; let's cc @grng3r as the author of that repository as well. I'm going to go ahead and nominate this so that we can get a 👍 (or not) at the T-compiler meeting confirming won't fix status. |
I made a fix in #73596, which also has a benefit of simplifying the rules slightly. |
Thanks guys, was more of a spelling mistake/leftover from previous version than unclear explanation of how to use shebang with rust as your previous explanation on how to use it worked fine in something else I was playing around with. But thank you very much for letting me know.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Sunday, 21 June 2020 22:33, Mark Rousskov ***@***.***> wrote:
I am inclined to close as won't fix; let's cc ***@***.***(https://github.com/grng3r) as the author of that repository as well.
I'm going to go ahead and nominate this so that we can get a 👍 (or not) at the T-compiler meeting confirming won't fix status.
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#73250 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AN63OYXEIVRKCCUHCBUAIL3RXZ4DNANCNFSM4N3WRJJA).
|
We fail to parse this (admittedly questionable) code as of beta:
https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=4fd6b726ceaddf0c06e67761d2276277
This broke one repository (not crate) in the beta crater run: https://crater-reports.s3.amazonaws.com/beta-1.45-1/beta-2020-06-03/gh/grng3r.rust_todo/log.txt
The text was updated successfully, but these errors were encountered: