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
The featureless entry point introduced in #2246 doesn't work for this case:
Suppose two contracts, "inner" and "outer", of which outer depends on inner.
When you run the optimizer, inner gets compiled first as primary package, where wasm exports are created.
Then, outer is compiled as primary package. Here, the intended way it would work is inner is compiled as a non-primary package, where wasm exports are NOT created.
However, since inner is already compiled as primary, cargo won't compiled it again. Cargo simply uses the primary build, which contains wasm exports. Thus, we get duplicate export error.