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
In answering a question on Stackoverflow, I came across an issue that I don't fully understand. Disregarding whether you actually need to use a deferred_type, the following fails:
so the types look pretty similar. Of course everything works fine if you specify the types, but instead define earth_model_type = EarthModel.class_type.instance_type directly instead of using the deferred_type.
The text was updated successfully, but these errors were encountered:
The reason for the error is that numba did not register a conversion of the deferred-type from its defined-type. It can be easily fixed by adding a can_convert_from() method to DeferredType.
But, should it?
I expect the DeferredType to be used only as the type of fields of aggregates that can refer to itself.
In answering a question on Stackoverflow, I came across an issue that I don't fully understand. Disregarding whether you actually need to use a
deferred_type
, the following fails:when running:
with the error:
If you instead allow numba to jit the function without supplying types:
and then this works and the result of
test.signatures
is:so the types look pretty similar. Of course everything works fine if you specify the types, but instead define
earth_model_type = EarthModel.class_type.instance_type
directly instead of using thedeferred_type
.The text was updated successfully, but these errors were encountered: