Skip to content

CompositeDisposable, Dispose() call order #3

Description

@pragmatrix

Just a thought, but when "disposable" objects do have dependencies among each other and were added to CompositeDisposable in their construction order, wouldn't it be better to dispose them in reversed order by default?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions