-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check use before defined in init exprs #26157
Open
arezaii
wants to merge
16
commits into
chapel-lang:main
Choose a base branch
from
arezaii:dyno-use-before-defined
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
dlongnecke-cray
approved these changes
Nov 14, 2024
arezaii
force-pushed
the
dyno-use-before-defined
branch
from
November 14, 2024 20:46
5f298c3
to
597b76f
Compare
arezaii
force-pushed
the
dyno-use-before-defined
branch
from
November 27, 2024 00:20
8bfc21d
to
1860214
Compare
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
arezaii
force-pushed
the
dyno-use-before-defined
branch
from
January 8, 2025 23:38
ba2320e
to
15dcba5
Compare
Signed-off-by: Ahmad Rezaii <[email protected]>
arezaii
force-pushed
the
dyno-use-before-defined
branch
2 times, most recently
from
January 14, 2025 20:12
b639c56
to
a88d486
Compare
Signed-off-by: Ahmad Rezaii <[email protected]>
arezaii
force-pushed
the
dyno-use-before-defined
branch
4 times, most recently
from
January 17, 2025 01:25
ae1709d
to
d210a64
Compare
Signed-off-by: Ahmad Rezaii <[email protected]>
arezaii
force-pushed
the
dyno-use-before-defined
branch
from
January 17, 2025 01:31
d210a64
to
aa050af
Compare
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
arezaii
force-pushed
the
dyno-use-before-defined
branch
from
January 23, 2025 18:05
577833c
to
816c5c3
Compare
Signed-off-by: Ahmad Rezaii <[email protected]>
Signed-off-by: Ahmad Rezaii <[email protected]>
arezaii
force-pushed
the
dyno-use-before-defined
branch
from
January 23, 2025 18:19
816c5c3
to
abeaa8a
Compare
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 updates how dyno detects use-before-definition errors. It should resolve https://github.com/Cray/chapel-private/issues/6666.
Fixing the missing error in Dyno updated the production error messages for use-before-define errors. Tests have been updated to reflect the changes.
A special case of use-before-defined for self-definition, has been added.
For example, given:
the previous production error would be:
The new production error will be:
and more detail can be viewed by compiling with
--detailed-errors
:Future work remains to specialize error messages for related cases when shadowing occurs. For example, the following codes exhibit self-definition and use-before-defined errors, respectively:
It would be nice to indicate to users that the outer variables in each case are supplanted by the local definition of a variable by the same name.
TESTING:
[Summary: #Successes = 17740 | #Failures = 0 | #Futures = 898]
[Summary: #Successes = 17924 | #Failures = 0 | #Futures = 909]