Lucas Kramer

Since having data nonterminals now muddies the terms vs. trees distinction, I'm leaning back towards "decorated" and "undecorated". So I think I now slightly prefer @RandomActsOfGrammar's suggestion of ``` local...

Coming back to this as the last dependency of #751. We never really settled on a syntax to use - going with `local nondec` and `production nondec` unless someone has...

Okay for now I'm going with `nondecorated local x::Type = ...;` or `nondecorated production x::Type = ...;`. Nondecorated locals can also just be abbreviated as `nondecorated x::Type = ...;`.

Since unlike Haskell we don't have infix operator functions in Silver, what should the equivalents of `` and `` for the `Applicative` type class be named? @remexre any suggestions?

I'm vetoing non-alphanumeric function names (and I'm sure Eric would if I didn't :-P) Those names seem reasonable. What's the reason for the seperate `Apply` and `Bind` type classes in...

I see your point, but a potential counterargument is that with the PureScript approach, to define a new instance of `Monad`, I would need to define instances for 5 classes,...

I guess this depends somewhat on how much work we want to do with the functor/applicative/monad hierarchy. I wasn't intending to do much with these besides reworking `do` notation and...

> go-to-def, etc. concurrent w/ rebuilds in LSP This doesn't really require the Silver compiler itself to be thread-safe. Each run of the Silver compiler produces a `Decorated Compilation` object....

Seems reasonable, not sure what the best syntax would be. Would prefer to not just use a symbol, but I would also like to minimize the number of things we...

#806 simply forbids file-scope `import silver:core;` for now.