-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fasta crash on nested generic function types #31213
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
Comments
cc @sigmundch |
VM support for nested generic function types in the Kernel FE should be ready. |
Currently, the Kernel FE doesn't set up parent pointers correctly for signature function types. This prevents type parameters on generic function types from being finalized correctly. In addition, finalization of generic interface types within a generic function type can crash if they reference not-yet-finalized type parameters of the enclosing function type. This review solves both issues. Several failing tests pass again, although more thorough testing is blocked on Github issue #31213 (nested generic function types crashing in Fasta). Bug: Change-Id: Ib5ee6b2566492e3fd6688fe5a6b6976692562ea1 Reviewed-on: https://dart-review.googlesource.com/16360 Reviewed-by: Régis Crelier <[email protected]>
When this issue is resolved, support for nested generic function types in the VM's Kernel FE should be tested further. |
Is running the above program in strong mode sufficient testing? |
We can't run the program at all through the Kernel FE since Fasta doesn't produce any output. |
Once this bug in Fasta has been fixed, what would you consider sufficient testing? The above program? |
It would definitely be a good start, although I would like to write some more involved tests as well. |
Thank you. In that case, I suggest you create a separate bug for tracking the test coverage. |
[email protected], [email protected] Bug: #31213 Change-Id: I0e791e20ac84d0bd3ddd0b2f9e489119a4eda9de Reviewed-on: https://dart-review.googlesource.com/18020 Reviewed-by: Sigmund Cherem <[email protected]> Commit-Queue: Konstantin Shcheglov <[email protected]>
The text was updated successfully, but these errors were encountered: