Lucas Kramer

I had a chat with Eric today about what this may look like in the future. The consensus for now was to stick with these explicit decorated wrapper productions and...

I think this should stay open for now, but I will at some point open a new tracking issue for the further work of introducing the alternate patterns for forwarding...

I think we now have everything needed in Silver to make this fairly straightforward - attribute occurs-on type constraints cover having `ast` (and also `unparse`, probably?) on `a`, and fixes...

One final note - I would consider this a prerequisite to dividing Silver into separate abstract and concrete syntax, if we ever decide to indeed go that route in the...

Note that while creating the above minimum example I was also able to cause an internal compiler error by changing `consBar` to `consBars` in the convenience aspect: ``` aspect genBars...

My vote is that this sort of documentation belongs on the website - there is already some similar (and largely duplicated) info at http://melt.cs.umn.edu/silver/dev/. But we should definitely add a...

The real reason you would want to do this is that it is a slightly nicer alternative to renaming imports. What would actually be nicer to have would be an...

Oh, I didn't realize that, good to know! It does seem like there should be a way of using a short qualified name instead of actually renaming the variable.

Looks like we decided on a solution but never actually fixed this - hackathon?

@tedinski I'm taking a look at performing the `PolyType` refactor, in preparation for implementing type classes. You mentioned in this issue that type classes would introduce a third constructor for...