Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"next year" and "in one year" should evaluate to the same date and time #15

Open
icnocop opened this issue Jul 12, 2016 · 0 comments
Open

"next year" and "in one year" should evaluate to the same date and time #15

icnocop opened this issue Jul 12, 2016 · 0 comments

Comments

@icnocop
Copy link

icnocop commented Jul 12, 2016

I expected that "next year" and "in one year" to evaluate to the same date and time, but they don't.

For example, given today's date and time of 7/11/2016 7:26 PM:

  • "next year" = 7/02/2017 12:00 AM
  • "in one year" = 7/11/2017 7:26 PM

I expected both to evaluate to 7/11/2017 7:26 PM.

Thank you.
@icnocop icnocop changed the title "next year" and "in one year" should evaluate to the same date "next year" and "in one year" should evaluate to the same date and time Jul 12, 2016
PipatPosawad pushed a commit to PipatPosawad/nChronic that referenced this issue Sep 8, 2016
robertwilczynski#15 add Sign class and SignScanner class
37da65b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@icnocop