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

Make std a feature, using #![no_std] otherwise #6

Closed
cuviper opened this issue Dec 19, 2017 · 0 comments
Closed

Make std a feature, using #![no_std] otherwise #6

cuviper opened this issue Dec 19, 2017 · 0 comments
Labels
breaking change enhancement
Milestone
num-complex-0.2

Comments

@cuviper
Copy link
Member

cuviper commented Dec 19, 2017

Depends on rust-num/num-traits#16, cc rust-num/num#216.
@cuviper cuviper mentioned this issue Dec 19, 2017
Closed
4 tasks
@cuviper cuviper mentioned this issue Jan 11, 2018
Merged
@cuviper cuviper added this to the num-complex-0.2 milestone Feb 7, 2018
@CAD97 CAD97 mentioned this issue Apr 26, 2018
Closed
3 tasks
@cuviper cuviper mentioned this issue May 10, 2018
Merged
bors bot added a commit that referenced this issue May 12, 2018
@bors @cuviper
Merge #22
6087ddf 
22: Add no_std support r=cuviper a=cuviper

Based on @termoshtt's #15, without the intrusive file splitting.  I also
addressed the other review comments I had left there.  The limitations
of `no_std` are the missing implementations of `Error` and methods based
on `Float`, although `FloatCore` is now used for a few things.  Format
widths are also not supported, as I couldn't find a way to do this
without using a temporary `String`.

Fixes #6.
Closes #15.

Co-authored-by: Josh Stone <cuviper@gmail.com>
@bors bors bot closed this as completed in #22 May 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change enhancement
Projects
None yet
Milestone
num-complex-0.2
Development

No branches or pull requests
1 participant
@cuviper