You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to implement fallible systems with legion? By fallible I mean avoiding .unwrap() and panics in the system and instead marshal the error back to the thread that actually started Schedule::execute.
So you could take that error and do something meaningful with it - maybe show an UI message box, log to console or retry etc.
Asking this as I though this is rather neat feature that seems to be supported natively in the new Sparsey ECS:
Is there any way to implement fallible systems with legion? By fallible I mean avoiding
.unwrap()
and panics in the system and instead marshal the error back to the thread that actually startedSchedule::execute
.So you could take that error and do something meaningful with it - maybe show an UI message box, log to console or retry etc.
Asking this as I though this is rather neat feature that seems to be supported natively in the new Sparsey ECS:
https://github.com/LechintanTudor/sparsey/blob/64367b8c1af647f09401d058334a42edaf231018/examples/errors.rs#L27-L32
The text was updated successfully, but these errors were encountered: