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
Here's just cloning the repo and trying to run the tests (note that the same error occurs if you try to run all tests for arrow2):
Compiling parquet2 v0.17.0error[E0425]: cannot find function `lz4_decompress_to_buffer` in this scope
--> src/compression.rs:196:13
|
196 | lz4_decompress_to_buffer(input_buf,Some(output_buf.len()asi32), output_buf)
| ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
error[E0425]: cannot find function `lz4_decompress_to_buffer` in this scope
--> src/compression.rs:265:33
|
265 | let decompressed_size = lz4_decompress_to_buffer(
| ^^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
I understand this has to do with lz4_flex and inconsistent feature sets, but having --all-features cause invalid feature sets is not very nice if it can be avoided.
lz4_decompress_to_buffer() is only defined for lz4 && !lz4_flex or for !lz4_flex && lz4, however that's not what the match checks. Perhaps lz4_flex && lz4 should be treated as lz4_flex for all intents and purposes? (so that --all-features would make sense)
(I know it's a breaking change but, just saying, another option is converting a feature, like lz4_flex, into a 'negative' feature, so that --all-features wouldn't enable it by default)
The text was updated successfully, but these errors were encountered:
Here's just cloning the repo and trying to run the tests (note that the same error occurs if you try to run all tests for arrow2):
I understand this has to do with
lz4_flex
and inconsistent feature sets, but having--all-features
cause invalid feature sets is not very nice if it can be avoided.lz4_decompress_to_buffer()
is only defined forlz4 && !lz4_flex
or for!lz4_flex && lz4
, however that's not what the match checks. Perhapslz4_flex && lz4
should be treated aslz4_flex
for all intents and purposes? (so that--all-features
would make sense)Here's what the match checks:
(I know it's a breaking change but, just saying, another option is converting a feature, like lz4_flex, into a 'negative' feature, so that
--all-features
wouldn't enable it by default)The text was updated successfully, but these errors were encountered: