---
title: "Discussion on \"🦀 My First Contribution to the Official Rust Repo 🦀\" | Hashnode"
description: "Discussion on \"🦀 My First Contribution to the Official Rust Repo 🦀\". New Rust contributor fixed a potential stack overflow issue in std::fs::create_dir_all() function"
url: "https://hashnode.com/posts/my-first-contribution-to-the-official-rust-repo/6964acb6b3cdc67daca35b9c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [🦀 My First Contribution to the Official Rust Repo 🦀](https://asder8215.com/my-first-contribution-to-the-official-rust-repo?utm_source=hashnode&utm_medium=feed)

New Rust contributor fixed a potential stack overflow issue in std::fs::create\_dir\_all() function

Jan 12 · 10 min read · asder8215.com  
Updated Jan 14  
Read the article

-   [#rust](https://hashnode.com/tag/rust)
-   [#opensource](https://hashnode.com/tag/opensource)

## Written by

[Mahdi Ali-Raihan](https://hashnode.com/@asder5124)

@asder5124

  
[View profile](https://hashnode.com/@asder5124)

Rust Developer who's interested in async and multithreading!

## Responses 1

Markdown supported · ⌘↵ to post

[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.
