# Hidden version of searchsortedfirst

**URL:** https://discourse.julialang.org/t/hidden-version-of-searchsortedfirst/131776
**Category:** General Usage
**Tags:** api, interface, methods, public
**Created:** [August 22, 2025, 1:57pm UTC](https://discourse.julialang.org/t/hidden-version-of-searchsortedfirst/131776 "2025-08-22T13:57:19Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![danielwe](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/danielwe/32/35657_2.png) [@danielwe](https://discourse.julialang.org/u/danielwe)
#### Post date: [August 23, 2025, 9:05pm UTC](https://discourse.julialang.org/t/hidden-version-of-searchsortedfirst/131776/5 "2025-08-23T21:05:09Z")

</div>

> [@nsajko](#):
>
> private methods are a bad practice, because:
> 
> - The concept seems to conflict with the new public API rules.
> - It introduces unnecessary concerns about method ambiguity.
> - It pollutes the output of reflection functionality such as `methods`.
> - Additional methods reduce compiler performance.

One more point: cycles in the call graph (on the level of functions, not methodinstances; we’re not talking about recursion here) can lead to history dependence in type inference. If compilation of the inner method is triggered independently before the outer method, type inference will often achieve better results than if the outer method is compiled first.

Details/links: [Type instability in nested quadgk calls - #21 by danielwe](https://discourse.julialang.org/t/type-instability-in-nested-quadgk-calls/126667/21)

---

_[View the full topic](https://discourse.julialang.org/t/hidden-version-of-searchsortedfirst/131776)._