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
Expected answer: 2
Actual answer: 3 ⚠️ In non-optimized mode (contextAtEachStep: [:c|]), the execution escapes from the simulator!
In Sandbox2, the issue does not occur.
The text was updated successfully, but these errors were encountered:
This makes sure that we finally can read our own writes during retracing, adhering to the normal execution semantics. Also, this fixes#52 as described in LinqLover/SimulationStudio#50.
Consequential changes:
- Update kernel tests: use exception handling protocol, update testGroups/expectedFailures
- Test read-your-own-writes
- Adjust proxy client code to honor the fact that implicit side-effects (different from the return value) are no longer possible:
* TDBCursor>>#livingHomeTraceFor:
* TDBInspector>>#replaceInspectorWithExplorer
+ Refactor view decoration in proxy holders: Always rebuild view (nuke deep model replacement) to avoid inconsistencies from first view. Improve MVC compatibility.
Given:
Expected answer:
⚠️ In non-optimized mode (
2
Actual answer:
3
contextAtEachStep: [:c|]
), the execution escapes from the simulator!In Sandbox2, the issue does not occur.
The text was updated successfully, but these errors were encountered: