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
According to Ts Generic Parameter Defaults doc there doesn't seem to be any inherent performance/flexibility downsides to set defaults for method generic types (where it makes sense).
For now, will keep generics defaults on method types to ensure maximum flexibility of changes for Fjl-v2.0.
Acceptance Criteria
Keep generic defaults, where they make sense, for method types:
Keep the defaults for:
Method "type" declarations - Ensures the [method] types stay flexible.
For methods that take multiple generics and have one or more of those generics take one the defined generics as a generic (think 'map' fn operation, etc.), in these cases it makes sense to have defaults as to make the methods easier to use.
According to Ts Generic Parameter Defaults doc there doesn't seem to be any inherent performance/flexibility downsides to set defaults for method generic types (where it makes sense).
For now, will keep generics defaults on method types to ensure maximum flexibility of changes for Fjl-v2.0.
Acceptance Criteria
Keep the defaults for:
Reference:
https://www.typescriptlang.org/docs/handbook/2/generics.html#generic-parameter-defaults
The text was updated successfully, but these errors were encountered: