Expose the useful constant values in TimeSpan

[IDisposable]

Make the useful constants that TimeSpan has internally declare public because they're rooted in hard reality and not changeable, and quite useful elsewhere.
Fixes #94545

[ghost]

Tagging subscribers to this area: @dotnet/area-system-datetime
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Make the useful constants that TimeSpan has internally declare public because they're rooted in hard reality and not changeable, and quite useful elsewhere.
Fixes #94545

Author:	IDisposable
Assignees:	-
Labels:	area-System.DateTime
Milestone:	-

[danmoseley]

Thanks, but the original issue needs to have the api-approved label before any PR. I suggest closing until then.

[IDisposable]

That's why it's Draft :)

[IDisposable]

Not sure why you would close a Draft... nor do I see how to reopen. That's not nice.

[danmoseley]

@IDisposable We have many active PR's which is why we ask to get approval on new API before starting a PR.

As far as I know you can reopen it - if you can't I'm not sure why 🙂

[tannergooding]

Notably, as per our CONTRIBUTING.md

Please do not:

...

• DON'T add API additions without filing an issue and discussing with us first. See API Review Process.

Every single PR opened has a cost, even for draft PRs. This comes in the form of e-mail notifications sent to developers, cross linking to the issues, time spent by developers who are giving the PR a preliminary glance, actual cost in terms of computing hours required to run tests and other validation, which in turn has downstream environmental impact and other considerations, etc.

There is nothing in this PR that requires it to be opened before the associated proposal goes to API review and so it is functionally noise until that occurs and it can opened if it gets approved.