Fix bugzilla 18552: Adds check bounds of year to std.datetime.date.Date

[denizzzka]

Fixes https://issues.dlang.org/show_bug.cgi?id=18552

[dlang-bot]

Thanks for your pull request and interest in making D better, @denizzzka! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + phobos#9025"

[jmdavis]

It's my understanding that the try-catch adds overhead. Given how often this code is going to be used with date/time stuff, it would make more sense to just check the bounds and throw rather than using to.

[denizzzka]

try-catch for .to isn't adds overhead here: if we just check bounds manually then create DateTimeException manually it will be same cost

Overhead here is added only by cost of the second exception creation only if bounds check failed. For year field it is very rare case and such approach makes code more common and clear.

So, since we're using exceptions in this module to report errors that's fine.