Skip to content

Find Intuitive Design For Determining Whether Channel Was Closed in Nested Function Call #222

@0xNeshi

Description

@0xNeshi

Currently, if a channel is detected as closed in a nested function call, we propagate either false or None, and in those cases just return; in the parent function.

Examples:

Ideally, the code should be self-explanatory and/or force us to handle channels closing in the parent function.
Consider:

  • using a new error type
  • custom enum ChannelState::Open / Closed
  • always propagating errors to the top-most parent function, that then streams the errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: refactorCode improvement without changing functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions