Run CI job to ensure no-std compatibility #26
Merged
Conversation
This file contains hidden or 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
Sympatron
force-pushed
the
check-no-std
branch
2 times, most recently
from
2f0d73a to
26c34de
Compare
Sympatron
force-pushed
the
check-no-std
branch
from
26c34de to
345a063
Compare
Sympatron
force-pushed
the
check-no-std
branch
from
345a063 to
7872924
Compare
sidcha
approved these changes
Nov 12, 2024
Member
sidcha
left a comment
sidcha
left a comment
There was a problem hiding this comment.
Huff, quite a bit of work to get this one pushed!
Thanks @Sympatron for the many PRs 🍾
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR introduces a CI job to ensure that
libosdpdoes not accidentally become incompatible withno-std. This will only work after goToMain/c-utils#28 (or similar) is merged.