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
the .convert() function needs an input type with a bound constraint on Coord<T> and produce an output type with a bound constraint on Coord<T>. However, the way it is defined today forces the 2 concrete types to be the same.
Note however that this would be a breaking change for the crate proj as now, the expected type should be made explicit and type inference might not always be able to save you.
The text was updated successfully, but these errors were encountered:
the
.convert()
function needs an input type with a bound constraint onCoord<T>
and produce an output type with a bound constraint onCoord<T>
. However, the way it is defined today forces the 2 concrete types to be the same.But it doesn't have to be like this. We could define the function as follows.
Note however that this would be a breaking change for the crate
proj
as now, the expected type should be made explicit and type inference might not always be able to save you.The text was updated successfully, but these errors were encountered: