Rust Ownership Explained with Python

Re:Rust Ownership Explained with Python by marcianx on Sunday September 30, 2018 @12:33AM (#18104470)

Rust does have these abstractions. The corresponding rust traits are `IntoIterator<Item=T>` and `Iterator<Item=T>`. For example:

  - Vec<T> implements IntoIterator<Item=T>
  - &Vec<T> implements IntoIterator<Item=&T>
  - &mut Vec<T> implements IntoIterator<Item=&mut T>

and consequently,

  - vec.into_iter() implements Iterator<Item=T>
  - (&vec).into_iter() (or vec.iter()) implements Iterator<Item=&T>
  - (&mut vec).into_iter() (or vec.iter_mut()) implements Iterator<Item=&mut T>

[ Parent | on HN ]

Re:Rust Ownership Explained with Python by lostmsu on Sunday September 30, 2018 @01:10AM (#18104570)

Good, but how do you create something, that is IntoIterator, which holds an immutable description of how to generate members to iterate over? And I mean some potentially infinite sequence.

[ Parent | on HN ]

Re:Rust Ownership Explained with Python by heinrich5991 on Sunday September 30, 2018 @02:16AM (#18104781)

For example like this: https://doc.rust-lang.org/std/iter/fn.repeat.html

[ Parent | on HN ]

Re:Rust Ownership Explained with Python by lostmsu on Sunday September 30, 2018 @01:33PM (#18107195)

Can you .map it?

[ Parent | on HN ]

Re:Rust Ownership Explained with Python by Darsstar on Sunday September 30, 2018 @04:50PM (#18108344)

Sure: https://play.rust-lang.org/?gist=1d5470a4649bb875581cc3dd9c5...

[ Parent | on HN ]