How do I collect into an array?

The issue is actually in collect, not in map.

In order to be able to collect the results of an iteration into a container, this container should implement FromIterator.

[T; n] does not implement FromIterator because it cannot do so generally: to produce a [T; n] you need to provide n elements exactly, however when using FromIterator you make no guarantee about the number of elements that will be fed into your type.

There is also the difficulty that you would not know, without supplementary data, which index of the array you should be feeding now (and whether it's empty or full), etc... this could be addressed by using enumerate after map (essentially feeding the index), but then you would still have the issue of deciding what to do if not enough or too many elements are supplied.

Therefore, not only at the moment one cannot implement FromIterator on a fixed-size array; but even in the future it seems like a long shot.

So, now what to do? There are several possibilities:

• inline the transformation at call site: [Value(1), Value(2), Value(3)], possibly with the help of a macro
• collect into a different (growable) container, such as Vec<Foo>
• ...

Update

This can work:

let array: [T; N] = something_iterable.[into_]iter() .collect::<Vec<T>>() .try_into() .unwrap() 

In newer version of rust, try_into is included in prelude, so it is not necessary to use std::convert::TryInto. Further, starting from 1.48.0, array support directly convert from Vec type, signature from stdlib source:

fn try_from(mut vec: Vec<T, A>) -> Result<[T; N], Vec<T, A>> { ... } 

Original Answer

as of rustc 1.42.0, if your element impl Copy trait, for simplicity, this just works:

use std::convert::TryInto; ... let array: [T; N] = something_iterable.[into_]iter() .collect::<Vec<T>>() .as_slice() .try_into() .unwrap() 

 collect as_slice try_into + unwrap() Iterator<T> ------> Vec<T> -------> &[T] ------------------> [T] 

But I would just call it a workaround. You need to include std::convert::TryInto because the try_into method is defined in the TryInto trait.

Below is the signature checked when you call try_into as above, taken from the source. As you can see, that requires your type T implement Copy trait, so theoritically, it will copy all your elements once.

#[stable(feature = "try_from", since = "1.34.0")] impl<T, const N: usize> TryFrom<&[T]> for [T; N] where T: Copy, [T; N]: LengthAtMost32, { type Error = TryFromSliceError; fn try_from(slice: &[T]) -> Result<[T; N], TryFromSliceError> { <&Self>::try_from(slice).map(|r| *r) } } 

For your specific problem, Rust 1.55.0 allows you to directly map an array:

enum Foo { Value(i32), Nothing, } fn main() { let bar = [1, 2, 3]; let foos = bar.map(Foo::Value); } 

While you cannot directly collect into an array for the reasons stated by the other answers, that doesn't mean that you can't collect into a data structure backed by an array, like an ArrayVec:

use arrayvec::ArrayVec; // 0.7.0 use std::array; enum Foo { Value(i32), Nothing, } fn main() { let bar = [1, 2, 3]; let foos: ArrayVec<_, 3> = array::IntoIter::new(bar).map(Foo::Value).collect(); let the_array = foos .into_inner() .unwrap_or_else(|_| panic!("Array was not completely filled")); // use `.expect` instead if your type implements `Debug` } 

Pulling the array out of the ArrayVec returns a Result to deal with the case where there weren't enough items to fill it; the case that was discussed in the other answers.

.collect() builds data structures that can have arbitrary length, because the iterator's item number is not limited in general. (Shepmaster's answer already provides plenty details there).

One possibility to get data into an array from a mapped chain without allocating a Vec or similar is to bring mutable references to the array into the chain. In your example, that'd look like this:

#[derive(Debug, Clone, Copy)] enum Foo { Value(i32), Nothing, } fn main() { let bar = [1, 2, 3]; let mut foos = [Foo::Nothing; 3]; bar.iter().map(|x| Foo::Value(*x)) .zip(foos.iter_mut()).for_each(|(b, df)| *df = b); } 

The .zip() makes the iteration run over both bar and foos in lockstep -- if foos were under-allocated, the higher bars would not be mapped at all, and if it were over-allocated, it'd keep its original initialization values. (Thus also the Clone and Copy, they are needed for the [Nothing; 3] initialization).

In this case you can use Vec<Foo>:

#[derive(Debug)] enum Foo { Value(i32), Nothing, } fn main() { let bar = [1, 2, 3]; let foos = bar.iter().map(|&x| Foo::Value(x)).collect::<Vec<Foo>>(); println!("{:?}", foos); } 

You may combine arrays map method with Iterator::next.

Example:

fn iter_to_array<Element, const N: usize>(mut iter: impl Iterator<Item = Element>) -> [Element; N] { // Here I use `()` to make array zero-sized -> no real use in runtime. // `map` creates new array, which we fill by values of iterator. let res = [(); N].map(|_| iter.next().unwrap()); // Ensure that iterator finished assert!(matches!(iter.next(), None)); res } 

UPD

After release of Rust 1.63, it is possible to use std::array::from_fn for this:

fn iter_to_array<Element, const N: usize>(mut iter: impl Iterator<Item = Element>) -> [Element; N] { let res: [_; N] = std::array::from_fn(|_| iter.next().unwrap()); // Ensure that iterator finished assert!(matches!(iter.next(), None)); res } 

You can actually define a Iterator trait extension to do this!

use std::convert::AsMut; use std::default::Default; trait CastExt<T, U: Default + AsMut<[T]>>: Sized + Iterator<Item = T> { fn cast(mut self) -> U { let mut out: U = U::default(); let arr: &mut [T] = out.as_mut(); for i in 0..arr.len() { match self.next() { None => panic!("Array was not filled"), Some(v) => arr[i] = v, } } assert!(self.next().is_none(), "Array was overfilled"); out } } impl<T, U: Iterator<Item = T>, V: Default + AsMut<[T]>> CastExt<T, V> for U { } fn main () { let a: [i32; 8] = (0..8).map(|i| i * 2).cast(); println!("{:?}", a); // -> [0, 2, 4, 6, 8, 10, 12, 14] } 

Here's a playground link.

This isn't possible because general arrays do not implement many traits. You can only collect into types which implement the FromIterator trait (see the list at the bottom of its docs).

This was a language limitation, since it is currently impossible to be generic over the length of an array and the length is part of its type. But, even if it were possible, it's very unlikely that FromIterator would be implemented on arrays because it'd have to panic if the number of items yielded wasn't exactly the length of the array.

The easiest way is to use the collect_array method of the excellent itertools crate. From their docs:

use itertools::Itertools; let iter = 1..3; if let Some([x, y]) = iter.collect_array() { assert_eq!([x, y], [1, 2]) } else { panic!("Expected two elements") } 

They avoid using a flexible-sized container (and therefore possible allocation) as described by some of the other answers.

I ran into this problem myself — here's a workaround.

You can't use FromIterator, but you can iterate over the contents of a fixed-size object, or, if things are more complicated, indices that slice anything that can be accessed. Either way, mutation is viable.

For example, the problem I had was with an array of type [[usize; 2]; 4]:

fn main() { // Some input that could come from another function and thus not be mutable let pairs: [[usize; 2]; 4] = [[0, 0], [0, 1], [1, 1], [1, 0]]; // Copy mutable let mut foo_pairs = pairs.clone(); for pair in foo_pairs.iter_mut() { // Do some operation or other on the fixed-size contents of each pair[0] += 1; pair[1] -= 1; } // Go forth and foo the foo_pairs } 

If this is happening inside a small function, it's okay in my book. Either way, you were going to end up with a transformed value of identical type as the same one, so copying the whole thing first and then mutating is about the same amount of effort as referencing a value in a closure and returning some function of it.

Note that this only works if you plan to compute something that is going to be the same type, up to and including size/length. But that's implied by your use of Rust arrays. (Specifically, you could Value() your Foos or Nothing them as you like, and still be within type parameters for your array.)