Skip to content

Fix communication object naming #101

Description

@mbianco

We should rename communication_object_2 into communication_object, and move the current communication_object into the benchmark folder, so we can test if there are overheads from having the more general co.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions