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

Determine the Buffer Representation #667

Closed
2 tasks done
iamrecursion opened this issue Feb 21, 2020 · 0 comments
Closed
2 tasks done

Determine the Buffer Representation #667

iamrecursion opened this issue Feb 21, 2020 · 0 comments
Assignees
Labels
-tooling Category: tooling p-medium Should be completed in the next few sprints

Comments

@iamrecursion
Copy link
Contributor

Summary

Given that we're going to be maintaining a set of edits on an internal representation of each open file, it's very important that we have a high-performance underlying representation that is amenable to editing.

Value

We will not run into memory or performance issues with the open buffers.

Specification

  • Determine which underlying structure is most appropriate for us to use.
  • This need not account for later use with CRDTs, but it is a bonus if it does.

Acceptance Criteria & Test Cases

  • We know which underlying structure we want to use to represent text buffers.
@iamrecursion iamrecursion transferred this issue from another repository Jun 23, 2020
@joenash joenash added -tooling Category: tooling Change: Non-Breaking p-medium Should be completed in the next few sprints 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
-tooling Category: tooling p-medium Should be completed in the next few sprints
Projects
None yet
Development

No branches or pull requests

3 participants