Adrian Sampson

I suppose my high-level point about the dilemma here is that we probably want to support both modes. That is, `seq { a ; b }` should keep its current...

It could work! Yeah, I think what's confusing here is that I also don't know what the right default is: schedulable vs. save-a-cycle. There is a reasonable argument to be...

This is great; thanks for the synopsis. And interesting that this example contains both static->dynamic and dynamic->static transitions!

Truly awesome; thanks for making this concrete, @calebmkim. That issue where the compiler would like to _add_ latency between `B` and the `static par` is exactly the situation I was...

Cool. That's a good plan… I share your aesthetic discomfort with semantics-bearing attributes, so I dig the idea of starting with one just because it's simpler to implement and then...

Indeed; thanks for the discussion! I too like the "forward declaration" idea. This seems like a good reflection of the needs of frontends that need to bring in their own...

All sounds awesome. I agree with the decisions you summarized briefly: * little endian * pad to bytes * row-major for multi-dimensional memories And very good reasoning about the metadata...

I don't remember of the top of my head where we landed on multi-dimensional memories, but IIRC we either (a) don't handle them at all, or (b) just report the...

Agreed; this hopefully should not affect what synthesis tools do. I guess I have learned never to trust synthesis tools to do anything, however, so it would of course be...

Sounds good overall! One thing I don't 100% understand: what's the motivation for getting rid of `StaticEnable`? Just curious; it probably doesn't matter too much.