Skip to content
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.

Generic annoyances. #694

Open
kiljacken opened this issue Feb 10, 2016 · 1 comment
Open

Generic annoyances. #694

kiljacken opened this issue Feb 10, 2016 · 1 comment

Comments

@kiljacken
Copy link
Member

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

@MovingtoMars
Copy link
Member

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants