No (not directly), it handles Vec<Data>... to have a Vec<Vec<String>> you'd have Vec<Data> with each Data being Vec<Data> of Data::String variant.
use data::Data;
fn main() {
// outer is Data::Vec or Vec<Data>
let outer: Data = Data::from(vec![
// This is also Data::Vec or Vec<Data>
Data::from(vec![
// And finally our strings
Data::from("Hello".to_string()),
Data::from("World".to_string())
])
]);
println!("outer = {}", outer);
}
This is more of a dynamic type, of select types. (String, i8 to i128, u8 to u128, f32 and 64, bool, Vec and HashMap allow for collections, with the ability of nesting)
Ah ha! Tests... I'm missing tests.
No (not directly), it handles `Vec<Data>`... to have a `Vec<Vec<String>>` you'd have `Vec<Data>` with each Data being `Vec<Data>` of `Data::String` variant.
```rust
use data::Data;
fn main() {
// outer is Data::Vec or Vec<Data>
let outer: Data = Data::from(vec![
// This is also Data::Vec or Vec<Data>
Data::from(vec![
// And finally our strings
Data::from("Hello".to_string()),
Data::from("World".to_string())
])
]);
println!("outer = {}", outer);
}
```
This is more of a dynamic type, of select types. (String, i8 to i128, u8 to u128, f32 and 64, bool, Vec<Data> and HashMap<String, Data> allow for collections, with the ability of nesting)
I don't see any tests.
Does this handle
Vec<Vec<String>>?Ah ha! Tests... I'm missing tests.
No (not directly), it handles
Vec<Data>... to have aVec<Vec<String>>you'd haveVec<Data>with each Data beingVec<Data>ofData::Stringvariant.This is more of a dynamic type, of select types. (String, i8 to i128, u8 to u128, f32 and 64, bool, Vec and HashMap allow for collections, with the ability of nesting)