Skip to content

Error provenance — identify which stream an error originated from #350

Description

@sgerbino

Summary

When an error is reported there is no way to figure out which stream it
originated from. The author accepted this should be fixed.

Detail

When an error is reported there is no way to figure out from which stream it
originated. This makes debugging and error handling harder in code that manages
multiple streams.

Acceptance criteria

  • A way to attribute a reported error to the originating stream.

References

Distinct from #298 (error dispositions).

Raised by Andrzej Krzemienski; Steve Gerbino agreed ("you're right about this
and we should fix it"). Source: Boost ML "[capy] error codes".

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions