[Request]: enable, or allow to opt-in rkyv
's strict
features
#3695
Labels
bug
Something isn't working
🎉 enhancement
New feature!
📦 lib-engine
About wasmer-engine
priority-high
High priority issue
🔈soundness
Bugs causing an unsound API
Milestone
Motivation
swc-project/swc#6922
There are couples of obscure report from plugin author / users of swc that plugin execution fails unexpectedly. It should have various different root cause, but one of them was identified as having different
rustc
compiler version can cause those. Per orignal PR's description and its comment swc-project/swc#6922 (comment), enablingstrict
in rkyv's serialization / deserialization would possibly resolve some of those issues via rkyv's gaurantee.SWC itself tried to apply those changes, however found out underlying
wasmer
(specificallywasmer-types
in wasmer@2) cannot be built when upstream SWC enables those features.Proposed solution
Basically request is enabling, or feature flag to support opt-in for rkyv's strict mode. Since SWC relies on wasmer@2 still, it'd be great if changes can be backported to @2 versions. I may try to make necessary changes myself if it is acceptable (and possible to release a new 2.x patch release).
Alternatives
SWC could try to fork wasmer@2, but that'll be too heavyweight option.
The text was updated successfully, but these errors were encountered: