I have an application where the package I am using requires the user to provide a function phi with calling statement like phi(a::Real)=.... I would like to pass additional function arguments args to phi. The way I have taken to get around this is to create an anonymous function a->myphi(a,args) tha…

Jake Roth! Maybe I’m missing something here, but a callable struct might be useful: mutable struct MyPhi <: Function # subtyping might be necessary stuff :: [...] end function (phi::MyPhi)(a) [...] end And then in your code you would create phi = MyPhi(other_args...), which you could then pas…

Are you sure allocations are happening at every loop iteration? I don’t think that should happen unless the types of the arguments change.

Ah, I wasn’t aware of this! Thanks Chris!

I think that you’re right! The allocations in --track-allocation=all don’t seem to show any. I’d originally found allocations when using @allocated on the single linesearch line of code. [Screen Shot 2023-02-16 at 6.09.37 PM]

Avoid allocating an anonymous function

General Usage

GHTaarn February 15, 2023, 4:13pm 4

Would you be able to simplify your code and still illustrate your problem? In item 5 in Please read: make it easier to help you this is suggested as one of the ways to make it easier for people to answer your question.

Topic		Replies	Views
Getting rid of memory allocations in nested functions Performance question , memory-allocation	3	391	January 31, 2023
To avoid allocations, avoid anonymous functions? New to Julia memory-allocation	5	1368	March 2, 2018
Understanding allocations when collapsing function arugments General Usage	15	975	April 20, 2021
Preallocating and returning anonymous function Performance	4	197	June 5, 2024
Avoiding memory allocation with function passed as argument Performance memory-allocation , argument , function	14	1211	September 2, 2021

Avoid allocating an anonymous function

Related topics