Remove support for 33+ flags and multiple returns #2050
Merged
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
This commit removes the feature gates of supporting 33-or-more flags in the component model and also being able to support named or multiple return types. These have been gated to return an error for some time now and no issues have arisen so now seems as good a time as any to remove the internal implementation details. This simplifies the representation of function return types and is intended to help make the internals here easier to understand for newcomers.
pchickey
approved these changes
Feb 13, 2025
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.
This commit removes the feature gates of supporting 33-or-more flags in the component model and also being able to support named or multiple return types. These have been gated to return an error for some time now and no issues have arisen so now seems as good a time as any to remove the internal implementation details. This simplifies the representation of function return types and is intended to help make the internals here easier to understand for newcomers.