Skip to content
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

executor buffer size should be customisable in no_std #18510

Open
mockersf opened this issue Mar 24, 2025 · 0 comments
Open

executor buffer size should be customisable in no_std #18510

mockersf opened this issue Mar 24, 2025 · 0 comments
Labels
A-Tasks Tools for parallel and async work C-Feature A new feature, making something new possible D-Unsafe Touches with unsafe code in some way O-Embedded Weird hardware and no_std platforms S-Needs-Design This issue requires design work to think about how it would best be accomplished X-Uncontroversial This work is generally agreed upon

Comments

@mockersf
Copy link
Member

          Correct, users currently don't have a way to customise this. To be honest, I don't like that it isn't a dynamic allocation like it is on `std` with `async-executor`. I'm happy to revert this change so that _users_ don't see any difference, and then we follow-up in 0.17 with a larger refactor/re-write of `bevy_tasks` (hopefully including Forte by then).

Originally posted by @bushrat011899 in #18506 (comment)

@mockersf mockersf added the O-Embedded Weird hardware and no_std platforms label Mar 24, 2025
@bushrat011899 bushrat011899 added C-Feature A new feature, making something new possible A-Tasks Tools for parallel and async work S-Needs-Design This issue requires design work to think about how it would best be accomplished X-Uncontroversial This work is generally agreed upon D-Unsafe Touches with unsafe code in some way labels Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Tasks Tools for parallel and async work C-Feature A new feature, making something new possible D-Unsafe Touches with unsafe code in some way O-Embedded Weird hardware and no_std platforms S-Needs-Design This issue requires design work to think about how it would best be accomplished X-Uncontroversial This work is generally agreed upon
Projects
None yet
Development

No branches or pull requests

2 participants