# Best practices for NonlinearSolve definition with temporary arrays

**URL:** <https://discourse.julialang.org/t/best-practices-for-nonlinearsolve-definition-with-temporary-arrays/115763>\
**Category:** New to Julia\
**Tags:** nonlinearsolve, solver\
**Created:** [June 17, 2024, 3:23pm UTC](https://discourse.julialang.org/t/best-practices-for-nonlinearsolve-definition-with-temporary-arrays/115763 "2024-06-17T15:23:16Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dieg0](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dieg0/32/210143_2.png) [@dieg0](https://discourse.julialang.org/u/dieg0)\
**Post date:** [October 6, 2024, 6:37pm UTC](https://discourse.julialang.org/t/best-practices-for-nonlinearsolve-definition-with-temporary-arrays/115763/5 "2024-10-06T18:37:42Z")

</div>

I did something akin to it. What @JonasWickman suggested works to make the function type stable. Other useful solutions imply using `@unpack` or `@pack` similar to [this](https://discourse.julialang.org/t/parsimonious-way-to-unpack-big-structs/66522/19).

---

_[View the full topic](https://discourse.julialang.org/t/best-practices-for-nonlinearsolve-definition-with-temporary-arrays/115763)._
