Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C cbl-gdb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • COBOLworx
  • cbl-gdb
  • Merge requests
  • !39

WIP: disabled core part for completion performance

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Simon Sobisch requested to merge ssobisch/cbl-gdb:patch-6 into version426 Apr 30, 2021
  • Overview 1
  • Commits 1
  • Pipelines 0
  • Changes 1

The question is: do we really need that check here in general any more?

If we need it I suggest to add a new parameter to this function and only test that depending on the context. The test would only be reasonable if:

  • we want to get the data
  • we already have checked that the limit is not exceeded (so first gather only the possibilities, then resolve them next)
Edited Apr 30, 2021 by Simon Sobisch
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: patch-6