-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add proper generic resolution in specialized nodes #546
Conversation
This will require a cleanup. I think a good way to think about the issue would be to split the problem into two traits: |
40c7908
to
33556ec
Compare
e51ed9e
to
38f7ca5
Compare
This comment was marked as resolved.
This comment was marked as resolved.
One of the problems remaining is the generation of new specialized nodes during a generic specialization phase. We need to figure out how to have proper, pretty and understandable code to do this |
4202c41
to
a928eab
Compare
cb3d847
to
2dbeaa8
Compare
Let's clean this up and merge it - It's getting really big and it's in a nice state of implementation right now. We can open up subsequent, smaller PRs for the remaining items of the issue |
aa4fcb8
to
694512a
Compare
What remains to do is to figure out a proper and clean way to create the specialized node, resolve its generic items, and then typecheck it before adding it to the context and specialized nodes