Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
L ldpl
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Lartu
  • ldpl
  • Issues
  • #104

Closed
Open
Created May 20, 2019 by Lartu@lartu🐕Maintainer

SPLIT should also store length

Created by: Lartu

LDPL vectors give no way to know their length. While I'd love to refactor them and make reading an index before it has been defined ilegal, this would break compatibility with older ldpl versions. So in order to know the length of a split, either the split function should return the length of the split vector or a way to know the lengh of a vector should be added to the language (in a way that makes sense).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking