Skip to content

Phase out CollectiveMonitorStateInternal #50

@srithon

Description

@srithon

We currently have CollectiveMonitorState separate from CollectiveMonitorStateInternal, but in order for the code to function we had to make CollectiveMonitorStateInternal publicly accessible. Because CollectiveMonitorState is just a RwLock wrapper around CollectiveMonitorStateInternal, we could probably flatten this hierarchy and get rid of the distinction quite easily.

Metadata

Metadata

Assignees

No one assigned

    Labels

    codebaseRelates to issues around code organization and other things unrelated to user experience

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions