Group imports and exports in exports module #2468
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
|
Okay I don't know if that works at the end of the day. Will try some more things based on that solution first. |
webmaster128
force-pushed
the
group-exports
branch
from
eddf68f to
7f63657
Compare
Merged
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.
Follow-up to #2467 and work towards #1962: Movin all imports and exports into a newly created exports folder we get increased visibility of the dependencies. Those work as follows.
This PR is a no-op, but after it we can cut out this entire tree for builds that target wasm32-unknown-unknown but not the main contract build by wrapping the contents of
src/exports/mod.rsin a macro you need to expand in a contract'slib.rs.