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

Implement Value Extraction from Scopes #779

Closed
iamrecursion opened this issue Nov 8, 2019 · 1 comment
Closed

Implement Value Extraction from Scopes #779

iamrecursion opened this issue Nov 8, 2019 · 1 comment
Assignees
Labels
--breaking Important: a change that will break a public API or user-facing behaviour p-high Should be completed in the next sprint

Comments

@iamrecursion
Copy link
Contributor

Summary

In order to implement lazy visualisations, a key feature of Enso Studio, we need the ability to execute arbitrary Enso code on values in the current frame. This execution mustn't be able to change the values in the scope, so we need to have some method for extracting those values from those scopes.

Value

This is the first of the two major building blocks to being able to provide lazy visualisations for Enso Studio.

Specification

  • Determine how best to extract values from the introspected scope in the interpreter without allowing any alteration to these values.
  • This value extraction should not impose significant performance or memory penalties, even in the case where the values contain huge amounts of data.
  • Implement this extraction functionality into the existing interpreter and provide an API.

Acceptance Criteria & Test Cases

  • The interpreter provides an API that allows for extracting values from the introspected interpreter scope.
  • This functionality is robust and rigorously tested.
@iamrecursion
Copy link
Contributor Author

Landed in #419.

@iamrecursion iamrecursion transferred this issue from another repository Jun 23, 2020
@iamrecursion iamrecursion added Category: Interpreter --breaking Important: a change that will break a public API or user-facing behaviour p-high Should be completed in the next sprint labels Jun 23, 2020
@iamrecursion iamrecursion mentioned this issue Jun 24, 2020
26 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--breaking Important: a change that will break a public API or user-facing behaviour p-high Should be completed in the next sprint
Projects
None yet
Development

No branches or pull requests

2 participants