Skip to content

Make names of Sender<> and Receiver<> variables more coherent #29679

@mrobinson

Description

@mrobinson

Sometimes these variables are called port, sometimes ipc, sometimes they have the name of the thread on the other end and sometimes not. My proposal is that we standardize on an obvious name for all of them:

  • layout_sender ← Always sends to the layout thread
  • layout_receiver ← Always receives from the layout thread
  • script_sender ← Always sends to the script thread
  • script_receiver ← Always receives from the script thread
  • constellation_sender ← Always sends to the constellation
  • constellation_receiver ← Always receives from the constellation thread
  • etc

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions