Remove restriction on the type of require results. #227
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
This comment was marked as resolved.
This comment was marked as resolved.
green-real
pushed a commit
to green-real/lute
that referenced
this pull request
May 19, 2025
We originally implemented a restriction on require results being a table or function so that scripts would intrinsically be forwards-compatible as they evolve. To my surprise, this is a controversial choice. As part of the as-of-yet-unwritten style guide of Lute, we'll never return anything that is not a table or function, but users are free to do how they see fit.
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.
We originally implemented a restriction on require results being a table or function so that scripts would intrinsically be forwards-compatible as they evolve. To my surprise, this is a controversial choice. As part of the as-of-yet-unwritten style guide of Lute, we'll never return anything that is not a table or function, but users are free to do how they see fit.