Implement IntoIterator for &{Path, PathBuf}

[apasel422]

Closes #26220.

r? @alexcrichton

[bluss]

if PathBuf should have a consuming iterator it's best to add it now (to not break .into_iter() later). I guess it's probably not going to have it?

[apasel422]

I'll look into adding it shortly.

On Monday, November 2, 2015, bluss notifications@github.com wrote:

if PathBuf should have a consuming iterator it's best to add it now (to
not break .into_iter() later). I guess it's probably not going to have it?

—
Reply to this email directly or view it on GitHub
#29514 (comment).

[apasel422]

@bluss Now that I'm looking into how this is implemented, I'm not sure what a consuming iterator for PathBuf would be.

[bluss]

Right, it doesn't seem to make sense. Sorry, just a knee-jerk check due to recent discussions where .into_iter() means .iter() for certain types.

[alexcrichton]

@bors: r+ 6ad6cc3

Thanks!

[bors]

⌛ Testing commit 6ad6cc3 with merge 3330f54...

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-debug-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-linux-cross-opt, auto-linux-musl-64-opt, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-gnu-32-nopt-t, auto-win-gnu-32-opt, auto-win-gnu-64-nopt-t, auto-win-gnu-64-opt, auto-win-msvc-32-opt, auto-win-msvc-64-opt