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
We had a specific use-case, where for YAML parsing we have a custom type namely "Nullable" as the following structure:
pubenumNullable<T>{/// Null valueNull,/// Value is presentPresent(T),}
This type behaves similar to Option type. Should we move towards generalizing the behaviour of the option type to any type that implements OptionalValue trait, which will define how to extract nested value for any type T.
We had a specific use-case, where for YAML parsing we have a custom type namely "Nullable" as the following structure:
This type behaves similar to Option type. Should we move towards generalizing the behaviour of the option type to any type that implements OptionalValue trait, which will define how to extract nested value for any type T.
?
The text was updated successfully, but these errors were encountered: