-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Matching on a str should compare content, not identity #673
Comments
This was a nonsense issue. Matching actually does the right thing. I am unsure why == does a different thing, but that's another story. |
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this issue
Dec 12, 2017
Add all current fallocate flags Also move them to the common Linux module, as they are not platform-specific. See include/uapi/linux/falloc.h.
ZuseZ4
pushed a commit
to EnzymeAD/rust
that referenced
this issue
Mar 7, 2023
* Add get type analyzer method to C API * Add inverted phi type handler
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
There was a regression introduced by b6e2bcad6cb that broke rmc --gen-c. This change fixes that. I am also fixing a random white space from my previous commit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Either that, or we should disallow it altogether. The current behaviour, where you can put a str in a case pattern, but there's no way to guarantee that any other str will equal the literal you put in there, seems bogus.
The text was updated successfully, but these errors were encountered: