Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
grew
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • grew
  • grew
  • Issues
  • #9

Closed
Open
Opened Apr 05, 2019 by GUILLAUME Bruno@guillaumOwner

Avoid duplicate solutions when several nodes are equivalent in patterns

When searching for a pattern like pattern { S -> N1; S -> N2; } each "occurrence" is given twice with N1/N2 exchanged. A trick to avoid this is to add N1 << N2 but this can be used only for ordered nodes.

A more general mechanism is needed in general:

  • option 1: add a syntax N1 <<< N2 to order node wrt their gid (👎 implementation dependant)
  • option 2: add a syntax like groups {N1; N2} (idem from previous but a little more abstract)
  • option 3: detect the subgroups of nodes that are equivalent (👎 difficult to implement)
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: grew/grew#9