-
Notifications
You must be signed in to change notification settings - Fork 305
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
refactor(wasm): modularize wasm crate logic #3432
Conversation
@hdevalence I'm realizing |
Yeah, I thought the reason for that was that it would be simpler to only pass one object over FFI into wasm. Even if it's a little inefficient, that's fine if the code becomes simpler, as long as it's not the dominant performance factor. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the wasm-compilation script, left comments in the other PR 👍
This PR is blocked until #3429 is merged. |
Follow-up to #3432. Shutting this customization off, because it was being ignored anyway, and generated a warnig: warning: profiles for the non root package will be ignored, specify profiles at the workspace root We should discuss whether keeping the wasm crate inside the workspace is the right move.
Follow-up to #3432. Shutting this customization off, because it was being ignored anyway, and generated a warnig: warning: profiles for the non root package will be ignored, specify profiles at the workspace root We should discuss whether keeping the wasm crate inside the workspace is the right move.
References #3431 and #3400.