You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be useful, for some situations, to allow the user to define a SpecificationGroup as parametric on constants that don't exist at the RoboChart level. These would then be treated the same as RoboChart constants for instantiatio npurposes.
Implementation-wise: This would require a more sophisticated scope resolution, as our current notion of 'constant = robochart, variable = robocert' would fail, as would the construction of parameterisations.
(This is actually the right repo now. Oops.)
The text was updated successfully, but these errors were encountered:
It may be useful, for some situations, to allow the user to define a SpecificationGroup as parametric on constants that don't exist at the RoboChart level. These would then be treated the same as RoboChart constants for instantiatio npurposes.
Implementation-wise: This would require a more sophisticated scope resolution, as our current notion of 'constant = robochart, variable = robocert' would fail, as would the construction of parameterisations.
(This is actually the right repo now. Oops.)
The text was updated successfully, but these errors were encountered: