Unexpected evaluation behavior for typed elements

[Daumantas]

I will see if we can figure something out.

Changed the search to consider owning types if a match was not found in current scope. Will be in either 0.8.2 release or the next after.

Otherwise, assert constraint { a.d == 15.0 } evaluating d not in the scope of a looks like a separate bug.

Already fixed for the next release, for Mass rollup example from Introduction to the SysML v2 Language - #15 by Daumantas