Remove re-export of types into top-level #303
Merged
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.
What
Remove the re-export of types into top-level that occurs when only one of the
curr
ornext
features are enabled.Why
It is confusing that when both
curr
andnext
are enabled that the top-level exports change. It's also difficult to debug.In most cases applications could just depend on the specific module they'd like to use, and as such can reference
stellar_xdr::curr::...
.