-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support no_std executors #3
Comments
I have one written here if it helps at all. https://github.com/richardanaya/executor I'm pretty interested in collaborating. I had a similar idea in my own package, but i'd be willing to conform to Agnostik's interface if its possible. |
Hi @richardanaya ! Great news, I would be very happy to incorporate your executor. The first thing comes into my mind is using your executor as defacto |
Absolutely! |
if you want you can open a PR and implement your executor. You just have to uncomment the |
Thanks! I tried integrating it this afternoon, I found some changes i need
to make to my library to be more compliant.
…On Tue, Mar 24, 2020 at 1:21 PM stu ***@***.***> wrote:
if you want you can open a PR and implement your executor. You just have
to uncomment the runtime_nostd in Cargo.toml and ci.sh and remove the core
dependency.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACHZGSXMNZWHDEZNQN5JMTRJEI5TANCNFSM4LSHQR6Q>
.
|
FYI, i'm no longer working on this as per #7. Someone else is free to take over. |
Since async / await is available in no_std environment now, agnostik should add a no_std runtime.
I'm not sure if it should implement an own no_std executor or using an already existing crate.
The text was updated successfully, but these errors were encountered: