Lucas Kramer
Lucas Kramer
Currently, when generating translation we only delete existing generated files from the directories corresponding to grammars that are being built; however files from grammars that no longer exist can persist...
Even with #670, there are still some situations for which a non-clean build can fail after some changes that should be okay. Consider the following: ``` grammar a; imports b;...
We currently hard-code the version number in the Silver driver, which is a bit suboptimal as it quickly can get out of date, and it would be more useful to...
Example: ``` nonterminal Foos; production consFoo top::Foos ::= Foos {} production nilFoo top::Foos ::= {} nonterminal Bars; production consBar top::Bars ::= Integer Bars {} production nilBar top::Bars ::= {} implicit...
On Wed, Jul 13, 2016 at 5:15 PM, Lucas Kramer [email protected] wrote: One major problem with how we do forwarding at the moment is that it will cause trees to...
As we somewhat recently discovered, Silver has decently good support for records via annotations (e.g. see [the refactor to `FlowEnv`](https://github.com/melt-umn/silver/pull/585/files#diff-653bee41354f2cc99d2ff0eb7f9e9c381b10c4d9bc31648dfc2ac24310fd69bf)). The one thing we lack is a corresponding notion of...
We make a decent effort to produce somewhat a somewhat readable Java translation (aside from the translation of deeply nested expressions, that's probably a lost cause...) However we use an...
In Haskell one can write e.g. `(==)` or `(a ==)` or `(== 2)` to partially apply the `==` operator. Silver has "attribute sections" inspired by this but not operator sections...
A thought I just had, somewhat related to IDE stuff - if we are going to have Silver generate various sorts of metadata for syntax highlighting from language specifications, it...
There don't appear to be any test cases for the flow analysis, besides just running it for ableC and other projects - but we should definitely be checking for regressions...