-
Notifications
You must be signed in to change notification settings - Fork 771
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
cargo doc fails with cannot find function bitwise_bin_op_simd_helper
when using features=["simd"]
#232
Comments
bitwise_bin_op_simd_helper
when using features=["simd"]
I guess there was a similar issue for 3.0.0, for this version it worked only with the combination Cf. https://issues.apache.org/jira/browse/ARROW-11387 and apache/arrow#9337. |
I just verified that this is still a problem with latest master from arrow-rs |
Does this mean that enabling the simd feature when using arrow as a dependency did not work at all? That would explain why I did not see any performance difference in benchmarks when enabling that feature recently. |
Ok, I did another test and now apparently this [package]
name = "foo"
version = "0.1.0"
authors = ["Ritchie Vink <ritchie46@gmail.com>"]
edition = "2018"
[dependencies]
arrow = {version="5.0.0-SNAPSHOT", git = "https://github.com/apache/arrow-rs", branch = "master", default-feature = false, features = ["simd"]} And the published version on [package]
name = "foo"
version = "0.1.0"
authors = ["Ritchie Vink <ritchie46@gmail.com>"]
edition = "2018"
[dependencies]
arrow = {version="4.0.0", default-features = false, features=["simd"]} with:
So apparently this bug is already fixed, but do we know what fixed it? |
This might have something to do with the crates.io releases. I am able to get a successful build from |
This was noticed by @ritchie46
cargo doc fails with
cannot find function bitwise_bin_op_simd_helper
when using features=["simd"]To Reproduce
Create a new empty repo
Add
to Cargo.toml
Then try to build docs:
The build fails:
Expected behavior
Documentation builds successfully, without error
The text was updated successfully, but these errors were encountered: