Support using both nullability and type overrides #549
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Implements support for using both nullability and type overrides at the same time, following the syntax proposed by @mehcode in #489.
as "ident"
emits eitherDbType
orOption<DbType>
depending on inferred nullabilityas "ident!"
emitsDbType
regardless of inferred nullabilityas "ident?"
emitsOption<DbType>
regardless of inferred nullabilityas "ident: Type"
emits eitherType
orOption<Type>
depending on inferred nullabilityas "ident!: Type"
emitsType
regardless of inferred nullabilityas "ident?: Type"
emitsOption<Type>
regardless of inferred nullabilityAt the moment, the wildcard syntax stays the same, and bothas "ident!: _"
andas "ident?: _"
result in a compile time parsing error.as "ident: _"
emits eithertry_get
ortry_get::<Option<_>, _>
depending on inferred nullabilityas "ident!: _"
emitstry_get
regardless of inferred nullabilityas "ident?: _"
emitstry_get::<Option<_>, _>
regardless of inferred nullabilityAddresses #489