Closed dhardy closed 1 month ago
The trip-hazard can also be resolved by making small_rng
a default feature.
Assuming SmallRng
implementation will continue to be part of the rand
crate, personally, I am fine with removing the feature.
minor thing but i like the consistency that every generator in rand::rngs
is gated behind a feature.
The trip-hazard can also be resolved by making small_rng a default feature.
agree
Summary
Remove
small_rng
feature, thus enablingSmallRng
by default and in all builds.Motivation
Less complexity. Removes a trip-hazard for new users: https://github.com/rust-random/rand/issues/1225
If I remember correctly, the motivation for feature-gating adding
small_rng
was to remove a dependency from builds which don't use it. Later, we decided to addstd_rng
for the same reason (even thoughThreadRng
requires it).We now define the two possible implementations of
SmallRng
in crate (around 250 LoC). If we changed the impl again, we'd very likely continue to do so (it would be unlikely to use more code).The additional (small) cost is that
SmallRng
must be compiled in all builds; linking should remove unused code thus not affecting binary size.