| commit | 622c7fb90f4b6973f4fef1149de92a76aa2c96ae | |
| author | Henri Verroken <hverr@fb.com> | |
| Wed, 1 Sep 2021 19:38:56 +0000 (1 12:38 -0700) | ||
| committer | Facebook GitHub Bot <facebook-github-bot@users.noreply.github.com> | |
| Wed, 1 Sep 2021 20:26:38 +0000 (1 13:26 -0700) | ||
| tree | 857a1b99ad1ad23153141fa24c06605110f430ba | treesnapshot (tar.gz zip) |
| parent | 590707df2169f8000be74a04bce6d6aa455bcd14 | commitdiff |
Build hashbrown with nightly flag
Summary:
Build hashbrown with the nightly flag enabled.
As part of a Hack project, we want to use hashbrown's HashMap with a custom allocator (short story: we want to have the HashMap live and allocate in shared memory).
However, to get access to this functionality, we must build the hashbrown crate with the nightly flag.
Is this dangerous?I [asked in **Rust at Facebook**](https://fb.workplace.com/groups/rust.language/posts/6375156715866223): the flag appears to be additive, so the consensus is that it's fine to enable this FB-wide
Reviewed By: mjhostet
Differential Revision: D30070281
fbshipit-source-id: f165ac1beaf5a44d5cb5b9012aebad5dc54beb95
Summary:
Build hashbrown with the nightly flag enabled.
As part of a Hack project, we want to use hashbrown's HashMap with a custom allocator (short story: we want to have the HashMap live and allocate in shared memory).
However, to get access to this functionality, we must build the hashbrown crate with the nightly flag.
Is this dangerous?I [asked in **Rust at Facebook**](https://fb.workplace.com/groups/rust.language/posts/6375156715866223): the flag appears to be additive, so the consensus is that it's fine to enable this FB-wide
Reviewed By: mjhostet
Differential Revision: D30070281
fbshipit-source-id: f165ac1beaf5a44d5cb5b9012aebad5dc54beb95
| hphp/hack/src/facts/ffi_bridge/Cargo.toml | diffblobblamehistory |