Implement proper no_std support
#12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While the crate claimed to support `no_std` this didn't seem to be true. However with the stabilization of alloc last year, more and more crates have added support for `no_std`. vek 0.10 just released with `no_std` support, so euc can now finally properly support `no_std` as well.
26 tasks
|
Thanks, I'll try to find time to work on this over the next week. |
|
Thanks very much for the PR! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While the crate claimed to support
no_stdthis didn't seem to be true. However with the stabilization of alloc last year, more and more crates have added support forno_std. vek 0.10 just released withno_stdsupport, so euc can now finally properly supportno_stdas well.