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
It seems that Context::executor was changed to return Option because in no_stdExecutor is not available.
However, the executor fn is not included when no_std is enabled. Given that Context::executor is present so that all callers can assume that an executor is present, would it be better for it not to return an Option?
Maybe if std is present, initializing a Context w/o a can panic?
The text was updated successfully, but these errors were encountered:
Yeah, I think this was a design mistake. I now have a design in mind that is no_std compatible and allows everyone to use executors, but I want to punt it to 0.3 (so we can go ahead and get 0.2 out the door). RFC coming soon.
It seems that
Context::executor
was changed to returnOption
because inno_std
Executor
is not available.However, the
executor
fn is not included whenno_std
is enabled. Given thatContext::executor
is present so that all callers can assume that an executor is present, would it be better for it not to return anOption
?Maybe if std is present, initializing a
Context
w/o a can panic?The text was updated successfully, but these errors were encountered: