Chris Dodd

Well, those specific examples that require local compile-time known values also require *numeric* type values, and instances are non-numeric (they are controls, parsers, externs, or actions), so there's no intersection....

They should be kept in sync as often as necessary and possible,

> * `bitvec[ expr : const ]` should hopefully be possible for the compiler to determine is type `bit` as long as `const` is a local compile-time known value, even...

In general, it is preferable to use names rather than node pointers, since, once you run the `UniqueNames` pass, all names will be "mangled" (have an _N suffixes added/modified as...

Being able to test this sort of thing is part of the impetus for #5123 -- that way we can have a command line argument that disables/changes some passes and...

> What is the behavior if you attempt to use an index expression that is not a compile-time known value? > > I could imagine trying to allow that if...

> Are the test failures unrelated to this PR? Other than that, the changes LGTM. I can't see any connection between the failure and this change -- something going awry...

> > Takeaways from LDWG: > > ``` > > * Would be great to have the property that these arrays can be desugared to basic primitives ideally in a...

Perhaps it would be good to include a statement along the lines of Expressions that are not compile-time-known values that are determined to be constant after some optimization passes may...

I don't think there's anything special about `in` arguments or directionless arguments -- implicit casts are allowed anywhere a type that can be implicitly cast to the type needed in...