Skip to content
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

fix generics treating symchoice symbols as uninstantiated #23860

Merged
merged 1 commit into from
Jul 19, 2024

Conversation

metagn
Copy link
Collaborator

@metagn metagn commented Jul 18, 2024

fixes #23853

Since #22610 generics turns the Name in the GT.Name expression in the test code into a sym choice. The problem is when the compiler tries to instantiate GT.Name it also instantiates the sym choice symbols. Name has type template (E: type ExtensionField) which contains the unresolved generic type ExtensionField, which the compiler mistakes as an uninstantiated node, when it's just part of the type of the template. The compilation of the node itself and hence overloading will handle the instantiation of the proc, so we avoid instantiating it in semtypinst, similar to how the first nodes of call nodes aren't instantiated.

@Araq Araq merged commit 97f5474 into nim-lang:devel Jul 19, 2024
18 checks passed
Copy link
Contributor

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from 97f5474

Hint: mm: orc; opt: speed; options: -d:release
173163 lines; 8.024s; 664.066MiB peakmem

narimiran pushed a commit that referenced this pull request Sep 13, 2024
fixes #23853

Since #22610 generics turns the `Name` in the `GT.Name` expression in
the test code into a sym choice. The problem is when the compiler tries
to instantiate `GT.Name` it also instantiates the sym choice symbols.
`Name` has type `template (E: type ExtensionField)` which contains the
unresolved generic type `ExtensionField`, which the compiler mistakes as
an uninstantiated node, when it's just part of the type of the template.
The compilation of the node itself and hence overloading will handle the
instantiation of the proc, so we avoid instantiating it in `semtypinst`,
similar to how the first nodes of call nodes aren't instantiated.

(cherry picked from commit 97f5474)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression - cannot instantiate Maybe generic arguments are missing
2 participants