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

several minor improvements #7

Merged
merged 1 commit into from Mar 27, 2021
Merged

several minor improvements #7

merged 1 commit into from Mar 27, 2021

Conversation

joseluis
Copy link
Contributor

most important:

  • include all features in docs.rs (compat module didn't show)
  • create both examples adapting them from the readme
  • impl RandomRange for u16, i8 & isize

also:

  • fix max values on several RandomRange impls, homogenize & rearrange them
  • reorganize and simplify Cargo.toml
  • fix a typo in the readme
  • run rustfmt

NOTE: I've left u32::MAX as the maximum number on [ui]64 & [ui]size for fear of overflowing, although I'm not sure of the underlying mechanics.

please let me know if you want something done differently.

- create both examples from the readme
- reorganize and simplify Cargo.toml
- include all features in docs.rs
- impl RandomRange for u16, i8 & isize
- fix max values on some RandomRange impls
- rearrange impls
- fix some typo
- run rustfmt
@not-fl3 not-fl3 merged commit d1fdee3 into not-fl3:master Mar 27, 2021
@not-fl3
Copy link
Owner

not-fl3 commented Mar 27, 2021

Awesome, thank you!

NOTE: I've left u32::MAX as the maximum number on [ui]64 & [ui]size for fear of overflowing, although I'm not sure of the underlying mechanics.

I believe it is good enough for now and I am also scared to change things.
However, it would be nice to make the maximum for u64 u64::MAX. As the first step for it, I would add some tests that rand is actually random enough and is not overflowing somewhere.

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

2 participants