Skip to content

Optimized cursor implementations #1142

Description

@colinodell

Currently, we have a single cursor implementation which must guard against / optimize for different scenarios such as:

  • Multi-byte vs ASCII strings
  • Lines with tabs
  • etc

Perhaps we should instead switch to an interface with multiple specialized implementations so that we can optimize the line-parsing based on these factors without needing to have multiple repeated checks across the various functions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    performanceSomething could be made faster or more efficient

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions