Enable @restrict for tuple parameters (follow-up to #5148)#5168
Open
gulugulubing wants to merge 1 commit into
Open
Enable @restrict for tuple parameters (follow-up to #5148)#5168gulugulubing wants to merge 1 commit into
gulugulubing wants to merge 1 commit into
Conversation
Member
|
Thanks! Something went wrong during the rebase though, there are still the 7 commits from #5148. We only need the latest 2. |
gulugulubing
force-pushed
the
fix-restrict-slice-tuple
branch
from
486077d to
f5ec1f4
Compare
Contributor
Author
OK. Fixed the git history. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #5148. The fix is a one-line change in dmd/typesem.d: when expanding a tuple parameter into individual elements, propagate
userAttribDeclfrom the outer parameter to each element.Also submitted upstream: dlang/dmd#23358.