---
title: "Comment by SMTasker on \"🦀 My First Contribution to the Official Rust Repo 🦀\" | Hashnode"
description: "One useful regression case for the iterative walk is a parent appearing between the upward scan and the downward creation pass. Pairing that with an existing no"
url: "https://hashnode.com/posts/my-first-contribution-to-the-official-rust-repo/6964acb6b3cdc67daca35b9c/comment/6ae68c1a5f630de902020944"
---

[Discussion](https://hashnode.com/posts/my-first-contribution-to-the-official-rust-repo/6964acb6b3cdc67daca35b9c)

Comment [🦀 My First Contribution to the Official Rust Repo 🦀](https://hashnode.com/posts/my-first-contribution-to-the-official-rust-repo/6964acb6b3cdc67daca35b9c)

[SMTasker](https://hashnode.com/@smtasker)

[Nov 1](https://hashnode.com/posts/my-first-contribution-to-the-official-rust-repo/6964acb6b3cdc67daca35b9c/comment/6ae68c1a5f630de902020944)

One useful regression case for the iterative walk is a parent appearing between the upward scan and the downward creation pass. Pairing that with an existing non-directory component would exercise the distinction you describe between AlreadyExists/is\_dir and errors that must propagate. It would also complement the deep-path test without relying on one platform's stack size.
