use strict provenance APIs on nightly#390
Conversation
|
Clippy has a bunch of complaints but those are not introduced by this PR. |
|
Strangely I don't see any permissive provenance warnings in the CI job for the first commit. Looks like these ZST code paths do not get executed in the test suite. I added a test for one of them, not sure how to reach the other ones. |
77265eb to
22bddc8
Compare
|
@bors r+ |
|
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message |
|
☔ The latest upstream changes (presumably #365) made this pull request unmergeable. Please resolve the merge conflicts. |
22bddc8 to
dd6aceb
Compare
|
@Amanieu I have rebased and resolved the conflicts. |
|
@bors r+ |
|
☀️ Test successful - checks-actions |
This makes hashbrown compatible with strict provenance, which helps Miri in ensuring pointers are used correctly.
Fixes #384