Lucas Kramer

What I don't get is why builds are actually sometimes failing from this, as opposed to simply swapping and running a bit slower?

... and it happened again: http://coldpress.cs.umn.edu:8080/job/melt-umn/job/ableC-sqlite/job/feature%252Fenv/15/consoleFull For some reason it only seems to be the sqlite extension acting up though. Not sure what is special about this one in particular.

Just changed it, Jenkins is building right now. We're probably fine going back to 6 executors, since after watching it for a bit we seem to be staying significantly under...

Semi-fixed on the Jenkins front with the move to foundry with oodles of RAM, but we would still like to reduce Silver's memory usage in general, and the above items...

Yeah, we already did this as a part of the origin tracking patch (settled on the syntax `attachNote note on e end`.) This restructuring is a mostly hypothetical exercise, which...

Do we really want to have libraries commonly used by extension writers under `silver:`? It seems to me that the `silver` top-level grammar should just be for the actual implementation...

The analogy here is to languages like java - we have `java.lang` imported by default. `lib:` really should go away, since we should only be 'claiming' the top-level grammar namespace...

Is there really a good reason to seperate these? To me it seems that these are just two different types of libraries that can be used by other extensions, and...

I see how having everything in one grammar could be simpler, but my concern is that people would find it seriously confusing to have the compiler implementation itself be one...

My point is that a DSL package such as `json` can still be considered a library, regardless of whether it contains functions, abstract productions, or concrete productions. `json` isn't something...