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
I could not find any example of a nullable type in a generic. Not a single List<String?> or Future<File?>.
For a regular Future<int> we use BridgeTypeAnnotation(BridgeTypeRef(CoreTypes.future, [CoreTypes.int])). For Future<int>? we could add , nullable: true to the annotation. But what to do when the generic type itself is optional?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I could not find any example of a nullable type in a generic. Not a single
List<String?>
orFuture<File?>
.For a regular
Future<int>
we useBridgeTypeAnnotation(BridgeTypeRef(CoreTypes.future, [CoreTypes.int]))
. ForFuture<int>?
we could add, nullable: true
to the annotation. But what to do when the generic type itself is optional?Beta Was this translation helpful? Give feedback.
All reactions