Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 830
    • Issues 830
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 240
    • Merge requests 240
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #17376
Closed
Open
Issue created Aug 27, 2018 by Sean Curtis@SeanCurtis-TRI

vtkNew move semantics

What are the odds of getting move semantics on a vtkNew object? Because the copy constructor and assignment have been explicitly deleted, that has dragged move semantics along with them. That makes the vtkNew class a not-quite unique_ptr making passing ownership impossible. I'm contemplating creating my own local version of vtkNew that has such semantics (and yet calls object->Delete() to otherwise maintain compatibility with the VTK garbage collection). It would be nicer if vtkNew were truly a VTK-branded unique_ptr.

Assignee
Assign to
Time tracking