Add nostd-entrypoint impls #8
Draft
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
|
What's the status of this PR? Anything I can do to help? |
Been MIA from travel / medical stuff, but should be able to tackle it this weekend! |
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.
Marked as a draft because I think half of this should go in, and the other half I mostly want to show to illustrate the problem we discussed in #1.
entrypoint_nostd!. See the examples for compare/contrast between the two styles of entrypoint.loader.rswas easy to adapt. The module structure here should have alib/src/loader/std.rswhere all the std contents live, and then switch on features to export*from either. Waited until last minute on that, to make rebasing to master more painless. Other than that, I think the nostd loader stuff is good to go.