Skip to content
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

rustc: [T, ..N] and [T, ..N+1] are not the same #14846

Closed
wants to merge 1 commit into from

Conversation

alexcrichton
Copy link
Member

This commit fixes a bug in the calculation of the hash of a type which didn't
factor in the length of a constant-sized vector. As a result of this, a type
placed into an Any of a fixed length could be peeled out with any other fixed
length in a safe manner.

This commit fixes a bug in the calculation of the hash of a type which didn't
factor in the length of a constant-sized vector. As a result of this, a type
placed into an Any of a fixed length could be peeled out with any other fixed
length in a safe manner.
@eddyb
Copy link
Member

eddyb commented Jun 12, 2014

I should've added a test for this, I believe @nick29581 reverted my previous fix.

@alexcrichton alexcrichton deleted the any-hash branch June 13, 2014 22:38
bors added a commit to rust-lang-ci/rust that referenced this pull request Nov 13, 2023
Switch to in-tree rustc dependencies with a cfg flag

We can use this flag to detect and prevent breakages in rustc CI. (see rust-lang#14846 and rust-lang#15569)

~The `IN_RUSTC_REPOSITORY` is just a placeholder. Is there any existing cfg flag that rustc CI sets?~
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants