Right now, the prototype imports and refers to the coreassertions version of a module, to avoid needing to set the various constants that are available on a module. Being able to capture certain properties of case studies means we'll need to pull various constants to different values, at which point we'll need to be
There are three phases here: decoupling ourselves from coreassertions (and replacing our code for looking up import files with the defs/ version used upstream); allowing constant definitions as part of a sequence; and allowing constant overrides as part of an assertion. This is the first one.
Right now, the prototype imports and refers to the coreassertions version of a module, to avoid needing to set the various constants that are available on a module. Being able to capture certain properties of case studies means we'll need to pull various constants to different values, at which point we'll need to be
There are three phases here: decoupling ourselves from coreassertions (and replacing our code for looking up import files with the
defs/
version used upstream); allowing constant definitions as part of a sequence; and allowing constant overrides as part of an assertion. This is the first one.