You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The requirements for @generated and @pure functions have changed in Julia v0.6. For instance, AFAIK you can no longer call any function function from a function generator which may be specialized in the future, or you risk getting a world age error. My understanding of this is that function generators are compiled just once, and immediately as they are read in by the system, so they only have access to methods before their definition. Furthermore, any methods found of a later world age will result in a world age related error. I think the reason for this is that pure functions and generators do not populate back-edges in the dependency graph for automatic recompilation, but @vtjnash knows the exact details.
A specific example is this line of Tensors where one and zero may fail on user defined types created after the user executes using Tensors. I haven't looked around for any more problems, but I thought I'd let you know after experience this in StaticArrays.
The text was updated successfully, but these errors were encountered:
The requirements for
@generated
and@pure
functions have changed in Julia v0.6. For instance, AFAIK you can no longer call any function function from a function generator which may be specialized in the future, or you risk getting a world age error. My understanding of this is that function generators are compiled just once, and immediately as they are read in by the system, so they only have access to methods before their definition. Furthermore, any methods found of a later world age will result in a world age related error. I think the reason for this is that pure functions and generators do not populate back-edges in the dependency graph for automatic recompilation, but @vtjnash knows the exact details.A specific example is this line of Tensors where
one
andzero
may fail on user defined types created after the user executesusing Tensors
. I haven't looked around for any more problems, but I thought I'd let you know after experience this in StaticArrays.The text was updated successfully, but these errors were encountered: