Trait-based error handling specification #5
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes
Emit
)#[sysfail(log)]
#3 (by using#[exclusive_sysfail]
)#[sysfail(Emit<AppExit>)]
)Changelog
#[quick_sysfail]
in favor of#[sysfail(Ignore)]
Option<()>
. Consider replacingoption?
byoption.ok(())?
log = "foo"
syntax byLog<ErrorType, Foo>
.the return type from your
#[sysfail]
systems.Failure
is now a trait on the error type returned by the#[sysfail]
system, rather than the whole return type.
Failure
now has an associated type:Param
. It allows accessing arbitrarysystem parameters in the error handling code.
FailureMode
toDedup
.bevy_mod_sysfail
directly depends onbevy
, rather than its subcratesfull
features, enabled by default. Disabling removes thebevy
dependency, to only depend on
bevy_ecs
, but at the cost of removingthe
Log
Failure
definition.Emit
Failure
, which sendsErr
s as bevyEvent
s.LogSimply
, a variant ofLog
that works withoutRes<Time>
Failure
trait.the bit of text before the "ERROR" colored text)
#[exclusive_sysfail]
, works like#[sysfail]
but is fully supportedby exclusive systems. It only supports
Failure
s whereParam = ()