Plenty of discussion has occured about approaches to solving performance of captured variables in closures · Issue #15276 · JuliaLang/julia · GitHub and examples of it rearing its ugly head, but I haven’t seen a succinct description of when it occurs and workarounds to fix that code. My immediate c…

Yes, this used to be more common — now it’s much more rare. In fact, many of the examples in the GitHub issue are fixed. Here’s a minor tip that I find to be good style and will help keep this gremlin away: avoid re-assigning to the same binding where possible. For example, the following function…

Documenting when the closure "bug" (#15276) binds, and how to avoid it for introductory users

General Usage

ChrisRackauckas July 25, 2018, 8:25am 3

The existence of a performance bug and bad coding practices are completely orthogonal ideas.

5 Likes

Topic		Replies	Views
Define data-dependent function, various ways New to Julia closure , functors	34	2451	November 2, 2020
Is a simple, beginner style with named parameters and no unnecessary type annotations acceptable? New to Julia	35	3356	February 9, 2018
Language restriction to solve 15276? Internals & Design	48	3998	May 11, 2018
Closures: Is this docs sentence still relevant? Performance closure	1	428	May 21, 2019
Passing a function as an argument via closure Performance question , package , performance , numerics , closure	9	1768	August 28, 2019

Documenting when the closure "bug" (#15276) binds, and how to avoid it for introductory users

Related topics