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

Add a test crate for testing no_std builds #139

Closed
Ogeon opened this issue Aug 10, 2019 · 0 comments · Fixed by #140
Closed

Add a test crate for testing no_std builds #139

Ogeon opened this issue Aug 10, 2019 · 0 comments · Fixed by #140
Labels
testing Improvements to (unit) testing code.

Comments

@Ogeon
Copy link
Owner

Ogeon commented Aug 10, 2019

As mentioned in #138 (comment), testing the no_std support seem to require a whole separate crate to avoid leaks from the dev dependencies. The current tests does not catch any compile errors from not having std, so this is necessary for knowing if that feature even works.

Also, if there is a better way, then that is of course preferred.
@Ogeon Ogeon added the testing Improvements to (unit) testing code. label Aug 10, 2019
@Ogeon Ogeon mentioned this issue Aug 11, 2019
Merged
bors bot added a commit that referenced this issue Aug 11, 2019
@bors @Ogeon
Merge #140
8951a44 
140: Add a basic test crate for no_std r=Ogeon a=Ogeon

It's very bare bones, but will hopefully get the job done.

Closes #139

Co-authored-by: Erik Hedvall <erikwhedvall@gmail.com>
@bors bors bot closed this as completed in #140 Aug 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
testing Improvements to (unit) testing code.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a basic test crate for no_std Ogeon/palette
1 participant
@Ogeon