Skip to content

Commit 389f286

Browse files
authored
Fix the TimeSpan comment about internal representation. (#78364)
1 parent 880a2e0 commit 389f286

File tree

1 file changed

+4
-4
lines changed
  • src/libraries/System.Private.CoreLib/src/System

1 file changed

+4
-4
lines changed

src/libraries/System.Private.CoreLib/src/System/TimeSpan.cs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,11 @@ namespace System
1212
// TimeSpan represents a duration of time. A TimeSpan can be negative
1313
// or positive.
1414
//
15-
// TimeSpan is internally represented as a number of milliseconds. While
16-
// this maps well into units of time such as hours and days, any
17-
// periods longer than that aren't representable in a nice fashion.
15+
// TimeSpan is internally represented as a number of ticks. A tick is equal
16+
// to 100 nanoseconds. While this maps well into units of time such as hours
17+
// and days, any periods longer than that aren't representable in a nice fashion.
1818
// For instance, a month can be between 28 and 31 days, while a year
19-
// can contain 365 or 364 days. A decade can have between 1 and 3 leapyears,
19+
// can contain 365 or 366 days. A decade can have between 1 and 3 leapyears,
2020
// depending on when you map the TimeSpan into the calendar. This is why
2121
// we do not provide Years() or Months().
2222
//

0 commit comments

Comments
 (0)