-
Notifications
You must be signed in to change notification settings - Fork 424
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resolve associative domain type expr module code in Dyno (#26077)
Get associative domain type expressions resolving using their module code in Dyno, and re-enable testing for them. This PR itself contains little work and mostly just drove Dyno work needed to support the module code. Contributes to Cray/chapel-private#6729. Also includes: - adding a dyno test for _rectangular_ domain literals - allowing `helpResolveFunction` to run on generic type constructors, per bug fix suggestion from Ben - adjusting the handling of `param == ?` comparisons which was introduced in #26219, so that it gets specially handled rather than trying to resolve a defined `==` operator - skipping recursing into `TupleDecl`s in `VarScopeVisitor` to delay [implementing call-init-deinit support for them](Cray/chapel-private#7021) for now - an out-of-scope fix in `CallInitDeinit::handleDeclarations` where we clearly meant to reference type expr, but used init expr - moving `makeParam[Int,String,Bool]` helpers in `prims.cpp` onto `QualifiedType` and use everywhere Future work: - resolve associative domain literals (#26534) - implement call-init-deinit for tuple splitting declarations/assignments (Cray/chapel-private#7021) [reviewed by @DanilaFe , thanks!] Testing: - [x] dyno tests - [x] paratest
- Loading branch information
Showing
15 changed files
with
304 additions
and
264 deletions.
There are no files selected for viewing
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 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 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 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 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 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 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 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 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
Oops, something went wrong.