I think you might have an older version of rust. 1.49 has stabilized the
feature.
I think we should test and specify a minimum rust version in our crates in
order to catch those errors.
On Thu, Feb 25, 2021, 18:36 Fernando Herrera <fernando.j.herr...@gmail.com>
wrote:
> It was a simple "cargo test" in the rust folder
>
> error[E0658]: binding by-move and by-ref in the same pattern is unstable
> > --> arrow/src/json/reader.rs:71:58
> > |
> > 71 | (InferredType::Array(s), InferredType::Array(o)) => {
> > | - by-ref pattern here ^ by-move
> > pattern here
> > |
> > = note: see issue #68354 <
> > https://github.com/rust-lang/rust/issues/68354> for more information
> > error[E0658]: binding by-move and by-ref in the same pattern is unstable
> > --> arrow/src/json/reader.rs:74:66
> > |
> > 74 | (InferredType::Scalar(self_hs),
> > InferredType::Scalar(other_hs)) => {
> > | ------- by-ref pattern here
> > ^^^^^^^^ by-move pattern here
> > |
> > = note: see issue #68354 <
> > https://github.com/rust-lang/rust/issues/68354> for more information
> > error[E0658]: binding by-move and by-ref in the same pattern is unstable
> > --> arrow/src/json/reader.rs:79:67
> > |
> > 79 | (InferredType::Object(self_map),
> > InferredType::Object(other_map)) => {
> > | -------- by-ref pattern here
> > ^^^^^^^^^ by-move pattern here
> > |
> > = note: see issue #68354 <
> > https://github.com/rust-lang/rust/issues/68354> for more information
> > error[E0658]: binding by-move and by-ref in the same pattern is unstable
> > --> arrow/src/json/reader.rs:91:17
> > |
> > 90 | InferredType::Array(self_inner_type),
> > | --------------- by-ref pattern
> > here
> > 91 | other_scalar @ InferredType::Scalar(_),
> > | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ by-move
> > pattern here
> > |
> > = note: see issue #68354 <
> > https://github.com/rust-lang/rust/issues/68354> for more information
> > error: aborting due to 4 previous errors
> > For more information about this error, try `rustc --explain E0658`.
> > error: could not compile `arrow`
>
>
> On Thu, Feb 25, 2021 at 5:34 PM Andrew Lamb <al...@influxdata.com> wrote:
>
> > Could you possibly provide the exact error message / steps to reproduce
> the
> > problem you are seeing? I wonder if some dependent library pushed an
> > incompatible upgrade or something like that
> >
> > On Thu, Feb 25, 2021 at 12:23 PM Fernando Herrera <
> > fernando.j.herr...@gmail.com> wrote:
> >
> > > Today I was running Rust tests on my fork in master and got an error
> > > message regarding flight. The message reads:
> > >
> > > binding by-move and by-ref in the same pattern is unstable
> > >
> > >
> > > Does anyone know what is wrong with flight?
> > >
> > > Thanks
> > > Fernando
> > >
> >
>
