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.

Sign up for GitHub

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

Jump to bottom

Will std::num::Float be moved here? #74

Closed
bvssvni opened this issue Apr 2, 2015 · 2 comments · Fixed by #75
Closed

Will std::num::Float be moved here? #74

bvssvni opened this issue Apr 2, 2015 · 2 comments · Fixed by #75

Comments

@bvssvni
Copy link
Contributor

bvssvni commented Apr 2, 2015

See PistonDevelopers/piston#864

We use the Float for generics in some piston libraries, and wonder what's the plan of replacing the trait.
@bvssvni bvssvni mentioned this issue Apr 2, 2015
Closed
@alexcrichton
Copy link
Contributor

Yes I believe the current plan is to move the generic traits into this crate for the time being.

cc @aturon

@aturon aturon mentioned this issue Apr 3, 2015
Merged
aturon added a commit to aturon/num that referenced this issue Apr 3, 2015
@aturon
Vendor deprecated/unstable traits from std::num
03db5c9 
This commit brings in a load of unstable and/or deprecated traits from
the `std::num` module. These traits provide for some degree of generic
programming over numeric types. They are not stable in `std` mostly
because we want more time to iterate on their design. Moving them to the
`num` crate allows existing code to keep using this functionality as we
do so.

Closes rust-num#74
@aturon
Copy link
Contributor

aturon commented Apr 3, 2015

See #75!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Vendor deprecated/unstable traits from std::num aturon/num
3 participants
@alexcrichton @aturon @bvssvni