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
{{ message }}
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.
I like the idea of an intermediate stage of code between semantic and codegen where interfaces are "flattened out" (this could be helpfulf for a lot of Ark-specific optimisations).
However, I think we should keep generic arguments how they are until after semantic because I think it gives much better error messages. There might be some more reasons to keep them, but I can't think of any right now.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I recently had to write a line of code which annoyed me greatly:
n.Assignment.GetType().BaseType.ActualType().(TupleType)
Is there any reason why we don't eliminate the generic arguments as early as possible so we can avoid wrapping types in yet another layer of stuff?
@MovingtoMars
The text was updated successfully, but these errors were encountered: