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
{{ message }}
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
NicholasLYang opened this issue
May 26, 2022
· 1 comment
Labels
A-ToolingArea: our own build, development, and release toolingI-StaffImplementation: should be in charge of a core member of the teamtaskA task, an action that needs to be performed
We've amassed quite a few views in the playground. Any more and we'll run into performance as well as usability issues.
One issue that adds to this is the run function in playground/src/lib.rs. It computes the data for all of the views at once. This isn't efficient as only one view is visible at a time. Instead we should have separate functions for each view, that way we can only compute that data.
However, we need to be a little careful, as passing the string from JavaScript to WebAssembly is very inefficient. Perhaps there is a way to persist the string on the Rust side and only update it when necessary. Alternatively, one could prove that this passing of the string is not a big deal (very possible!).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-ToolingArea: our own build, development, and release toolingI-StaffImplementation: should be in charge of a core member of the teamtaskA task, an action that needs to be performed
Description
We've amassed quite a few views in the playground. Any more and we'll run into performance as well as usability issues.
One issue that adds to this is the
run
function inplayground/src/lib.rs
. It computes the data for all of the views at once. This isn't efficient as only one view is visible at a time. Instead we should have separate functions for each view, that way we can only compute that data.However, we need to be a little careful, as passing the string from JavaScript to WebAssembly is very inefficient. Perhaps there is a way to persist the string on the Rust side and only update it when necessary. Alternatively, one could prove that this passing of the string is not a big deal (very possible!).
The text was updated successfully, but these errors were encountered: