Skip to content

Default LocalDate invalid in non-intuative ways #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
GoogleCodeExporter opened this issue Mar 15, 2015 · 6 comments
Closed

Default LocalDate invalid in non-intuative ways #116

GoogleCodeExporter opened this issue Mar 15, 2015 · 6 comments
Labels
Milestone

Comments

@GoogleCodeExporter
Copy link

If you create a default LocalDate with new LocalDate() or default(LocalDate) or 
by not assigning to a LocalDate field and then compare it to another (i.e. 
date1.Equals(date2)), you will get a null reference exception.

I understand that the default value is an invalid value by design, but it 
should really throw an exception to that effect rather than the null exception.

I'm using 1.0.0-beta2

Original issue reported on code.google.com by WalkerCo...@gmail.com on 5 Oct 2012 at 6:30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants