Jonathan Lindegaard Starup
Jonathan Lindegaard Starup
Manually rewriting blacken to a non-flat pattern match could undermine a potential cool pattern match desugaring extension. Maybe pattern match improvement is cool enough for an intern. There is even...
By PR discussion it seems current approach is stuck, so I'm labeling it stuck
I hope this doesn't result in hardcoded IDs spread throughout the compiler that you manually have to verify are disjoint
One place (file, object, whatever) could have a list/map of error names and IDs. It's just bad if its spread across files
> What is notable is that the constraint: Why is it notable? > For each equation with a concrete effect, e.g.: from your example, do you mean "for each equation...
> >What does this mean? how do you "chain through" a variable? > > It means there is dataflow, i.e. through an equality. `Console` could also flow into `ef` via...
> As for spreading the numbers all over, the point is that these numbers do not affect anything in the compiler. Its not like some hard control or dataflow dependency....
If you don't like strings and `.getClass.getName` you can also make a `sealed trait ErrorCase` and have a case object for each. You're right that this can result in desync,...
I don't know if it's for the initial version, but we use singleton objects a couple places (unit, nullary tags) and I'm not sure how that fits in here. They...
@magnus-madsen didn't to full detail, but i am happy