# Confusing results when searching documentation, 1.3.1

**URL:** <https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542>\
**Category:** General Usage\
**Created:** [January 19, 2020, 10:24am UTC](https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542 "2020-01-19T10:24:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcreel](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mcreel/32/30088_2.png) [@mcreel](https://discourse.julialang.org/u/mcreel)\
**Post date:** [January 19, 2020, 10:24am UTC](https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542/1 "2020-01-19T10:24:30Z")

</div>

Searching the 1.3.1 documentation for “closure” yields 16 results, one of which is the “Closures” section. Searching for “closures” or “Closures” gives 14 results, which do not contain the section. If desired, I can make a PR.

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [January 19, 2020, 10:29am UTC](https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542/2 "2020-01-19T10:29:22Z")

</div>

Have you tried the developer version?  
[https://docs.julialang.org/en/v1.5-dev/search/?q=closure](https://docs.julialang.org/en/v1.5-dev/search/?q=closure)  
It is getting better I think.

---

<div class="post-metadata">

**Author:** ![mcreel](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mcreel/32/30088_2.png) [@mcreel](https://discourse.julialang.org/u/mcreel)\
**Post date:** [January 19, 2020, 11:49am UTC](https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542/3 "2020-01-19T11:49:53Z")

</div>

Great! Thanks!

As a suggestion for additional improvements, I find that discussion of mutating functions (those that end with !) is pretty hard to locate. It’s under [https://docs.julialang.org/en/latest/manual/style-guide/#Append-!-to-names-of-functions-that-modify-their-arguments-1](https://docs.julialang.org/en/latest/manual/style-guide/#Append-!-to-names-of-functions-that-modify-their-arguments-1), but this seems like a pretty important feature to not have a more specific entry.

---

<div class="post-metadata">

**Author:** ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)\
**Post date:** [January 19, 2020, 12:39pm UTC](https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542/4 "2020-01-19T12:39:17Z")

</div>

This is not a feature of the language though. Appending `!` to a functions name will not magically make it mutate its argument, it’s merely a style choice to inform users of the function to be aware of the fact that the function they’re calling is implemented in such a way as to mutate its arguments.

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [January 19, 2020, 6:44pm UTC](https://discourse.julialang.org/t/confusing-results-when-searching-documentation-1-3-1/33542/5 "2020-01-19T18:44:35Z")

</div>

> [@Sukera](#):
>
> it’s merely a style choice

While technically true, is a pretty strong language convention. It’s used throughout Base, the standard library, and most of the major packages. In other words,

> [@mcreel](#):
>
> this seems like a pretty important feature to not have a more specific entry.

Has a lot of merit.