From 2daf45db7bd306af2c0d3dd2264358d95d1054e6 Mon Sep 17 00:00:00 2001 From: Aaron Hill Date: Wed, 30 Oct 2019 15:02:39 -0400 Subject: [PATCH] Use `slice::iter` instead of `into_iter` to avoid future breakage `an_array.into_iter()` currently just works because of the autoref feature, which then calls `<[T] as IntoIterator>::into_iter`. But in the future, arrays will implement `IntoIterator`, too. In order to avoid problems in the future, the call is replaced by `iter()` which is shorter and more explicit. --- src/operators/arrange/arrangement.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/operators/arrange/arrangement.rs b/src/operators/arrange/arrangement.rs index 81264b4b6..fa1f607f8 100644 --- a/src/operators/arrange/arrangement.rs +++ b/src/operators/arrange/arrangement.rs @@ -393,7 +393,7 @@ where let frontier = [ capability.as_ref().map(|c| c.time().clone()), input1.frontier().frontier().get(0).cloned(), - ].into_iter().cloned().filter_map(|t| t).min(); + ].iter().cloned().filter_map(|t| t).min(); if let Some(frontier) = frontier { trace.as_mut().map(|t| t.advance_by(&[frontier]));