max-sixty opened a new issue, #3849:
URL: https://github.com/apache/arrow-rs/issues/3849

   **Describe the bug**
   <!--
   A clear and concise description of what the bug is.
   -->
   
   Currently `arrow-rs` doesn't compile successfully with the full range of 
dependencies in its `Cargo.toml`. 
   
   This is similar to the issue reported by 
https://github.com/apache/arrow-rs/issues/3525. That was closed with a 
suggestion to bump dependencies, but doesn't help for other projects that want 
to test that their Cargo is accurate — 
https://github.com/wangfenjin/duckdb-rs/pull/135 & 
https://github.com/PRQL/prql/pull/2112. The intention behind `Cargo.toml` is 
that it specifies the full range of dependencies, IIUC.
   
   **To Reproduce**
   <!--
   Steps to reproduce the behavior:
   -->
   
   ```
   cargo +nightly update -Z minimal-versions
   cargo build
   ```
   
   ```
   error[E0599]: no method named `powi` found for struct `f16` in the current 
scope
      --> arrow-array/src/arithmetic.rs:351:25
       |
   351 |                 Ok(self.powi(exp as i32))
       |                         ^^^^ method not found in `f16`
   ...
   380 | native_type_float_op!(f16, f16::ONE, f16::ZERO);
       | ----------------------------------------------- in this macro 
invocation
       |
       = help: items from traits can only be used if the trait is in scope
       = note: this error originates in the macro `native_type_float_op` (in 
Nightly builds, run with -Z macro-backtrace for more info)
   help: the following traits are implemented but not in scope; perhaps add a 
`use` for one of them:
       |
   18  | use num::Float;
       |
   18  | use num::traits::float::FloatCore;
       |
   18  | use num::traits::real::Real;
       |
   ...
   ```
   
   Thank you!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to