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
Description:
When discussing #26798 in the team meeting today, there was some uncertainty about the return type used for totalMicroseconds. The user requesting the feature proposed it using int and the main reason totalSeconds uses real seems to be because it must divide the number of microseconds to determine the total number of seconds used. Additionally, there were tests that had used totalSeconds similarly to how totalMicroseconds would be used and some of them explicitly cast the result to an int.
Note that since the type argument would have a default value of the type returned by the methods today, this would not be considered a breaking change on timeDelta.totalSeconds (which is otherwise considered stable) unless we decided to use a different default type for the argument.
Is this issue currently blocking your progress?
no, it was just something that occurred to us
Code Sample
use Time;
var a =new timeDelta(microseconds=10);
writeln(a.totalMicroseconds(t=real));
The text was updated successfully, but these errors were encountered:
Summary of Feature
Description:
When discussing #26798 in the team meeting today, there was some uncertainty about the return type used for
totalMicroseconds
. The user requesting the feature proposed it usingint
and the main reasontotalSeconds
usesreal
seems to be because it must divide the number of microseconds to determine the total number of seconds used. Additionally, there were tests that had usedtotalSeconds
similarly to howtotalMicroseconds
would be used and some of them explicitly cast the result to anint
.Note that since the type argument would have a default value of the type returned by the methods today, this would not be considered a breaking change on
timeDelta.totalSeconds
(which is otherwise considered stable) unless we decided to use a different default type for the argument.Is this issue currently blocking your progress?
no, it was just something that occurred to us
Code Sample
The text was updated successfully, but these errors were encountered: