-
Notifications
You must be signed in to change notification settings - Fork 292
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
Introduce ahash-compile-time-rng
feature.
#125
Introduce ahash-compile-time-rng
feature.
#125
Conversation
3fe2350
to
2907d9b
Compare
Clippy seems to be failing due to a new lint. Could you add Also, could you document the feature in |
Disables the default features of `ahash` and reintroduces them through a new feature called `ahash-compile-time-rng`, which is enabled by default. The new feature makes it possible for depended crates to rely on `hashbrown` with `ahash` as default hasher and to disable the `compile-time-rng` at the same time. This might be useful for any dependent crate targeting `no_std`, which contains `rand` or `rand_core` somewhere inside the dependency tree as a bug in cargo accidentally enables the underlying `getrandom` feature if `compile-time-rng` is enabled [1]. ... fixes rust-lang#124 [1] rust-lang/cargo#5760
2907d9b
to
43911e5
Compare
Added new commit to fix this.
Amended the documentation to the original commit. |
43911e5
to
388287c
Compare
You need to run |
388287c
to
92bc9f8
Compare
@bors r+ |
📌 Commit 92bc9f8 has been approved by |
Introduce `ahash-compile-time-rng` feature. **Content** Disables the default features of `ahash` and reintroduces them through a new feature called `ahash-compile-time-rng`, which is enabled by default. The new feature makes it possible for depended crates to rely on `hashbrown` with `ahash` as default hasher and to disable the `compile-time-rng` at the same time. This might be useful for any depended crate targeting `no_std`, which contains `rand` or `rand_core` somewhere inside the dependency tree as a bug in cargo accidentally enables the underlying `getrandom` feature if `compile-time-rng` is enabled [1]. ... fixes #124 [1] rust-lang/cargo#5760 --- **Warnings** (1) Compiling `ahash` with disabled `compile-time-rng` feature is currently broken and requires tkaitchuck/aHash#25 to be merged in advance. (2) This introduces a hidden behavior change for all dependent crates, using hashbrown with `default-features = false` and `features = 'ahash'`. This happens as the `ahash` feature no longer implicitly enables the `compile-time-rng` feature of `ahash`. --- Is the naming of the feature okay? Do I need to add any additional changes?
☀️ Test successful - checks-travis |
Content
Disables the default features of
ahash
and reintroduces themthrough a new feature called
ahash-compile-time-rng
, which isenabled by default.
The new feature makes it possible for depended crates to rely on
hashbrown
withahash
as default hasher and to disable thecompile-time-rng
at the same time.This might be useful for any depended crate targeting
no_std
,which contains
rand
orrand_core
somewhere inside the dependencytree as a bug in cargo accidentally enables the underlying
getrandom
feature if
compile-time-rng
is enabled [1].... fixes #124
[1] rust-lang/cargo#5760
Warnings
(1) Compiling
ahash
with disabledcompile-time-rng
feature is currently broken and requires tkaitchuck/aHash#25 to be merged in advance.(2) This introduces a hidden behavior change for all dependent crates, using hashbrown with
default-features = false
andfeatures = 'ahash'
. This happens as theahash
feature no longer implicitly enables thecompile-time-rng
feature ofahash
.Is the naming of the feature okay? Do I need to add any additional changes?