Been struggling to figure out why accesses to these struct fields are causing memory allocations. Here is my test code: module AllocationsTest struct SubStruct a::Float64 b::Float64 end struct AllocationsStruct arr::Array{SubStruct} end function make() subStructArr = Array{SubStr…

[image] dellagd: struct AllocationsStruct arr::Array{SubStruct} end Array{T} is not a concrete type. Array{T,1} (or equivalently Vector{T}) is. You are missing this type parameter, so the field is abstractly typed. In your second, parametric version you almost get there except you write …

Why is Julia allocating when accessing these structs?

General Usage Performance

lmiq June 10, 2024, 2:05pm 19

Yes, pass the data as parameters to the function. That’s the point.

Topic		Replies	Views
Allocation during access to "typed" field of mutable struct Performance question	11	997	November 18, 2021
Struct and memory allocation Performance memory-allocation	4	355	January 10, 2024
Unexpected performance outcome. Does accessing struct members cause allocation? General Usage performance	18	392	October 16, 2024
Allocations on field access even though no abstract types are involved General Usage	9	147	March 7, 2025
A question about how arrays work, how memory is allocated and what happen when chunks of code inside a function are moved into another function Performance	10	458	May 13, 2022

Why is Julia allocating when accessing these structs?

Related topics