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

fix: compilation errors with --no-default-features #59

Merged
merged 12 commits into from
Apr 11, 2022

Conversation

hawkw
Copy link
Owner

@hawkw hawkw commented Apr 11, 2022

This fixes compilation for no-std targets. My bad --- I was checking
this manually and never added a CI job for it.

This branch adds a CI check that the crate compiles with
--no-default-features, and fixes a number of issues that broke the
no-std build:

  • f8d9527 fix(no_std): fix warning in resume_unwind
  • cbf943a fix(no_std): fix compilation error in unreachable_unchecked
  • 8ae178a fix(no_std): remove use of thread::panicking
  • dab0d49 fix(alloc): fix missing Box imports
  • 208defc fix(no_std): wrong feature gate for println macros

Fixes #58

@hawkw hawkw enabled auto-merge (squash) April 11, 2022 23:47
@hawkw hawkw merged commit a2ab178 into main Apr 11, 2022
@hawkw hawkw deleted the eliza/fix-no-std-build branch April 11, 2022 23:54
hawkw added a commit that referenced this pull request Apr 12, 2022
<a name="v0.1.2"></a>
### v0.1.2 (2022-04-12)

#### Bug Fixes

*   compilation errors with `--no-default-features` (#59) ([a2ab178](a2ab178), closes [#58](#58))
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.

crate does not compile as no_std
1 participant