diff --git a/my_qustions_and_ai_answers/Map struct _ not related to hashmap b/my_qustions_and_ai_answers/Map struct not related to hashmap similarity index 99% rename from my_qustions_and_ai_answers/Map struct _ not related to hashmap rename to my_qustions_and_ai_answers/Map struct not related to hashmap index 9d4238f..0102a17 100644 --- a/my_qustions_and_ai_answers/Map struct _ not related to hashmap +++ b/my_qustions_and_ai_answers/Map struct not related to hashmap @@ -148,4 +148,4 @@ Here are a few reasons why the Map struct is needed: From a user's perspective, you don't need to worry about the Map struct directly. The Rust standard library provides a clean and ergonomic interface for working with iterators, and the existence of the Map struct is an implementation detail that allows the iterator infrastructure to function correctly and efficiently. -When you call `.map(closure)` on an iterator, you're creating a new iterator of type `Map`, but you can treat it like any other iterator and continue chaining other adapter methods or consuming the iterator as needed. \ No newline at end of file +When you call `.map(closure)` on an iterator, you're creating a new iterator of type `Map`, but you can treat it like any other iterator and continue chaining other adapter methods or consuming the iterator as needed.