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
Following #488 arrow-rs compiles to wasm32-unknown-unknowm only with the "js" feature of rand enabled. However, when the "js" feature is enabled the produced wasm modules are no longer stand alone and require JavaScript, which is not necessarily available. For example, these modules can't run in runtimes like wasmer (in contrast to modules compiled to wasm32-unknown-unknowm with arrow-rs 4.x).
Describe the solution you'd like
Make rand an optional dependency so we can opt out. In arrow2 this is already the case (and at least there rand is only used in benchmarks).
Describe alternatives you've considered
If it's only use for benchmarks and testing in arrow-rs too then make it an optional dependency that is only enabled when feature flags for benchmarks are set (if that exists already).
The text was updated successfully, but these errors were encountered:
Following #488 arrow-rs compiles to wasm32-unknown-unknowm only with the "js" feature of rand enabled. However, when the "js" feature is enabled the produced wasm modules are no longer stand alone and require JavaScript, which is not necessarily available. For example, these modules can't run in runtimes like wasmer (in contrast to modules compiled to wasm32-unknown-unknowm with arrow-rs 4.x).
Describe the solution you'd like
Make rand an optional dependency so we can opt out. In arrow2 this is already the case (and at least there rand is only used in benchmarks).
Describe alternatives you've considered
If it's only use for benchmarks and testing in arrow-rs too then make it an optional dependency that is only enabled when feature flags for benchmarks are set (if that exists already).
The text was updated successfully, but these errors were encountered: