Add support for explicit export specifications and legacy modules #227
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
radbasa
pushed a commit
to Appsilon/box
that referenced
this pull request
Jul 1, 2024
…mr#227) * Add test case for legacy modules feature * Add test case for explicit exports * Add `export` function * Add documentation of `export` functionality
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.
Add the
box::exportfunction which can be used instead of (not in addition to!)@exporttags. This function can also be used to declare that a module has no exports.The semantics of exporting were changed such that modules without any exports are now treated as legacy R script modules, and all visible names are exported by default. To retain the old functionality of exporting o names,
box::export()can be added to such modules.This improves support for legacy R scripts, and thus fixes #207.