Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK-m VTK-m
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 193
    • Issues 193
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 38
    • Merge requests 38
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTK-mVTK-m
  • Issues
  • #6
Closed
Open
Created Jun 12, 2015 by Robert Maynard@robertmaynardContributor

Make Predicate, Unary, and Binary Operator template parameter names consistent

Current the template names for the Predicate, or Operator changes for each Device Adapter algorithm. Shouldn't we have consistent names?

Maybe the following names should be used.

  1. Predicate: takes a single parameter, and returns bool
  2. BinaryCompare: takes two parameters, and returns bool, used for strict weak ordering
  3. BinaryEquiv: takes two parameters, and returns bool, used for equivilancy
Assignee
Assign to
Time tracking