Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D dune-istl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Core Modules
  • dune-istl
  • Issues
  • #44
Closed
Open
Created Jan 02, 2018 by Oliver Sander@oliver.sanderOwner

Precise semantics of OwnerOverlapCopyCommunication not documented

The documentation of the OwnerOverlapCopyCommunication class says:

A class setting up standard communication for a two-valued
attribute set with owner/overlap/copy semantics.

What does this mean precisely? In particular:

  • what does for a two-valued attribute set mean?
  • What is the definition of owner/overlap/copy semantics?

This may all be obvious to the experts, but for the rest of us a more detailed description would be very helpful. It that description is given here in the thread I volunteer to turn it into a patch.

Assignee
Assign to
Time tracking