Implement RustcDecodable and RustcEncodable for arrays. about rustc-serialize

[WildCryptoFox]

You might want to parse to a Vec<T>; then handle that directly.

[alexchandel]

Ideally I'd like to avoid the cost of allocating and pushing to a vector, and I'd like to serialize a struct with an array member.

[WildCryptoFox]

IIRC; you've already allocated for the parser before it even handles your types.

[alexchandel]

And yet, using a Vec instead of a [T; n] introduces additional allocation into my types and code. It also deletes the type safety I had in using fixed-length arrays, instead forcing me to manually check the length of a vector. That is not the right design.

[WildCryptoFox]

Tuples were manually handled as with macros; IIRC, there is some work (at least on the TODO for rust) to enable having traits against numeric types. A concept whose name I can't recall right now - but will allow us to implement over all lengths of any T, and work with numbers in the types.. Ex. fn f<T>(a: [T; n], b: [T; m]) -> [T; n+m] {...}