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
Currently, Duration exposes a bunch of canned fields like Zero, OneMinute,
NegativeOneTick, and so on. It also exposes sensible operator overloads and
factory methods, meaning that it's unclear as to whether 'a duration of three
days' should be best constructed via:
Duration.OneStandardDay * 3
I suggest that we pick one, and I'd tend toward the factory methods, rather
than trying to provide a bunch of fields for 'common but not really' durations.
Alternatively, we should remove the factory methods (apart from FromTimeSpan())
and rationalise the common durations (removing NegativeOneTick in favour of
-OneTick and adding OneStandardWeek). But I'd prefer the former, I think.
Original issue reported on code.google.com by malcolm.rowe on 20 Apr 2012 at 1:47
The text was updated successfully, but these errors were encountered: