问题描述
LocalDate＃toDateMidnight 的javdoc如下所示：
午夜在某些时区不存在的事实似乎足以避免完全使用 DateMidnight （假设你的代码没有使用已知不是固定的时区，有这个DST情况，将来永远不需要使用不同的时区）。
但是， DateMidnight 是不被弃用，并且在javadoc中没有类似的推荐或警告，对于 DateMidnight 类本身。此外， DateMidnight 构造函数乐意接受即时和时区，使得午夜在给定的日期不存在，而不是抛出 IllegalArgumentException like LocalDate＃toDateMidnight 。
$ b在$ {code> DateMidnight 的行为就像一个 DateTime $ b
当某一天不存在午夜时，为什么 LocalDate＃toDateMidnight 抛出异常，而 DateMidnight 构造函数不？如果有的话， DateMidnight 的推荐用例是什么？
使用 DateMidnight 不是很好的理由。 LocalDate 是更好的选择。这是因为午夜在某些时区每年不会发生一次，完全弄乱了课堂的可用性，并在应用程序中创建了错误。
构造函数已修复为避免最坏的问题，但是看到内部毫秒值指向01:00的 DateMidnight 对象并不是很好。
The javdoc for LocalDate#toDateMidnight reads as follows:
The fact that midnight does not exist in certain time zones seems like reason enough to avoid using DateMidnight entirely (assuming your code is not using a fixed time zone that is known not to have this DST situation and will never need to use different time zones in the future).
However, DateMidnight is not deprecated and there is no similar recommendation or warning in the javadoc for the DateMidnight class itself. Furthermore, the DateMidnight constructor happily accepts an instant and time zone such that midnight does not exist on the given day, rather than throwing an IllegalArgumentException like LocalDate#toDateMidnight. The resulting DateMidnight behaves like a DateTime with time at start of day.
When midnight does not exist on a given day, why does LocalDate#toDateMidnight throw an exception while the DateMidnight constructor does not? What is the recommended use case for DateMidnight if any?
There is no good reason to use DateMidnight. LocalDate is the better option. Thats because midnight does not occur once a year in certain time-zones, completely messing up the usability of the class, and creating bugs in applications.
The constructor was fixed to avoid the worst problem, however seeing a DateMidnight object with the internal millisecond value pointing at 01:00 isn't exactly great.
这篇关于推荐用于Joda-Time的DateMidnight的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！