141 fix behavior of virtualfilesystem functions in blockingnon async context #143
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.
This pull request removes the usage of the
futurescrate throughout the codebase, replacing all references and usages with the project's owntaskmodule. This affects dependency management, code imports, and all instances where asynchronous blocking was performed. The change streamlines async handling and reduces external dependencies.Dependency and workspace cleanup:
futuresfrom the workspace dependencies, member list, and individual crateCargo.tomlfiles, includingdrivers/native,drivers/wasm,modules/abi/context,modules/abi/definitions,modules/bindings/host, andmodules/bootsplash. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]Code refactoring:
futures::block_oncalls withtask::block_onin Rust source files, including device operations, window management, file system functions, memory allocation, and bindings. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]Minor UI adjustment:
KEYBOARD_SIZE_RATIOfrom4.0 / 1.0to3.0 / 1.0inexecutables/shell/graphical/src/layout.rsto adjust keyboard sizing.