You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make tests for all of the major pairs of name shadowing and ensure that they behave as expected, i.e. the "newer" name is used when expected and there's a name resolution conflict when expected:
module name
package name
global constant
let binding
function: name, generic parameter, parameter
trait: name, generic parameter, method name
struct: name, field
match pattern
lambda function parameter
conflict between dependencies
Project Impact
Nice-to-have
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered:
# Description
## Problem\*
Resolves#4672
## Summary\*
The plan is to generate variations of a test program that checks for
several types of name shadowing, and then ensure that we get expected
results or errors for different combinations of name conflicts.
## Additional Context
## Documentation\*
Check one:
- [x] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist\*
- [x] I have tested the changes locally.
- [x] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
---------
Co-authored-by: jfecher <[email protected]>
Co-authored-by: Tom French <[email protected]>
Co-authored-by: Tom French <[email protected]>
Problem
We could have more tests for name shadowing.
Happy Case
Make tests for all of the major pairs of name shadowing and ensure that they behave as expected, i.e. the "newer" name is used when expected and there's a name resolution conflict when expected:
Project Impact
Nice-to-have
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: