Skip to content

Allow for outgoing error reporting using GLOBAL_ERROR_HANDLER / set_error_handler #19466

Open
@m-edlund

Description

@m-edlund

What problem does this solve or what need does it fill?

For automatic error reporting to be possible using the global bevy error handler, there needs to be a way to send out errors from the ErrorHandler function. Currently this is not possible, since the ErrorHandler type does not accept closures, and does not give access to the world.

What solution would you like?

Give world access in the ErrorHandler function, or allow for closures to be used as ErrorHandlers, so that a channel can be captured and used to send out error information.

What alternative(s) have you considered?

The alternative is piping every single fallible system into an error handler, which seems like the exact thing a global error aims to solve.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-ECSEntities, components, systems, and eventsC-FeatureA new feature, making something new possibleM-Needs-Release-NoteWork that should be called out in the blog due to impactS-Needs-DesignThis issue requires design work to think about how it would best be accomplishedX-UncontroversialThis work is generally agreed upon

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions