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 preparation for dart-lang/sdk#55062, we need to change the structure of JObject to be composed of a JReference instead of inheriting one. This makes it more natural, where a JObject is a JReference and a JType and the JReference itself is responsible for its life cycle and not the JObject (See #970 (comment)).
This potentially enables us to have multiple kinds of JReferences like JGlobalReference and JWeakGlobalReference or a global reference that is not managed by a native finalizer.
For version 0.8.0, we can land these changes all at once:
In preparation for dart-lang/sdk#55062, we need to change the structure of
JObject
to be composed of aJReference
instead of inheriting one. This makes it more natural, where aJObject
is aJReference
and aJType
and theJReference
itself is responsible for its life cycle and not theJObject
(See #970 (comment)).This potentially enables us to have multiple kinds of
JReference
s likeJGlobalReference
andJWeakGlobalReference
or a global reference that is not managed by a native finalizer.For version 0.8.0, we can land these changes all at once:
JObject
JMethodIDPtr
andJFieldIDPtr
into high level classes #985JObject
s across isolates #1054JObject
generic methods likecallMethodByName
#549The text was updated successfully, but these errors were encountered: