ZonedDateTime.Equals fails when using BCL-based zones #334

Closed
GoogleCodeExporter opened this Issue Mar 15, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@GoogleCodeExporter
See http://stackoverflow.com/questions/26874303

Basically because we don't support comparing BCL-based time zones for equality, 
we don't support comparing ZDT values either, which really sucks.

It may be fixed for 2.0 already - I can't remember offhand what I've done about 
ZDT equality.

Original issue reported on code.google.com by jonathan.skeet on 12 Nov 2014 at 5:41

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 15, 2015

This issue was closed by revision 70facc93dd52.

Original comment by jonathan.skeet on 26 Feb 2015 at 9:53

  • Changed state: Fixed
This issue was closed by revision 70facc93dd52.

Original comment by jonathan.skeet on 26 Feb 2015 at 9:53

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 15, 2015

This issue was closed by revision 6a9a6c2da216.

Original comment by jonathan.skeet on 26 Feb 2015 at 9:53

This issue was closed by revision 6a9a6c2da216.

Original comment by jonathan.skeet on 26 Feb 2015 at 9:53

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 15, 2015

Original comment by malcolm.rowe on 27 Feb 2015 at 10:27

  • Added labels: Milestone-1.3.1
  • Removed labels: Milestone-1.3.1-consider

Original comment by malcolm.rowe on 27 Feb 2015 at 10:27

  • Added labels: Milestone-1.3.1
  • Removed labels: Milestone-1.3.1-consider

@malcolmr malcolmr added the bug label Mar 15, 2015

@malcolmr malcolmr modified the milestone: 1.3.1 Mar 15, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment