Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reevaluate trace #24

Open
4 tasks
LinqLover opened this issue Jan 23, 2022 · 0 comments
Open
4 tasks

Reevaluate trace #24

LinqLover opened this issue Jan 23, 2022 · 0 comments
Labels
engineering Technical change to the machinery

Comments

@LinqLover
Copy link
Collaborator

LinqLover commented Jan 23, 2022

Build an API to reevaluate a trace from an earlier point in time in a forked memory (#27).

In the context of the UI, this would be relevant for the following operations:

  • accept contents to inspector field (currently changes the present state, unclear semantics)
  • debug it from code pane/inspector field (could spawn another trace debugger)
  • return value from context (not yet implemented)
  • skip context (not yet implemented)

Technically, TDBRetracingSimulator could detect state changes and offer the client to reevaluate the trace automatically. See "retrace side effects" in the design process document.

Could either be solved via rematerialization (#23) into a copy or by melting a tracing simulator and a retracing simulator properly.

@LinqLover LinqLover added the engineering Technical change to the machinery label Jan 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Technical change to the machinery
Projects
None yet
Development

No branches or pull requests

1 participant