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.

Sign up for GitHub

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

Jump to bottom

Interpret Display or Debug on arbitrary memory locations #14

Open
oli-obk opened this issue Feb 5, 2019 · 2 comments
Open

Interpret Display or Debug on arbitrary memory locations #14

oli-obk opened this issue Feb 5, 2019 · 2 comments

Comments

@oli-obk
Copy link
Owner

oli-obk commented Feb 5, 2019

No description provided.

@bjorn3
Copy link
Collaborator

bjorn3 commented Feb 5, 2019

I would like to prevent Display or Debug to have no side effects here, because that would be plain confusing to people. Maybe add some way to clone an EvalContext? That would also make it possible to make reverse debugging less expensive by storing an EvalContext every n steps. And then step from there to the right position on a back step.

@bjorn3
Copy link
Collaborator

bjorn3 commented Feb 5, 2019

I would also like to have the option to print all locals using Debug when available, so Vec shows its contents.

@DJMcNab DJMcNab mentioned this issue Mar 15, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oli-obk @bjorn3