|Blaine Motsinger 8a69928c56 solved leap||1 year ago|
|README.md||1 year ago|
|cases_test.go||1 year ago|
|leap.go||1 year ago|
|leap_test.go||1 year ago|
Given a year, report if it is a leap year.
The tricky thing here is that a leap year in the Gregorian calendar occurs:
on every year that is evenly divisible by 4 except every year that is evenly divisible by 100 unless the year is also evenly divisible by 400
For example, 1997 is not a leap year, but 1996 is. 1900 is not a leap year, but 2000 is.
If your language provides a method in the standard library that does this look-up, pretend it doesn’t exist and implement it yourself.
Though our exercise adopts some very simple rules, there is more to learn!
For a delightful, four minute explanation of the whole leap year phenomenon, go watch this youtube video.
You will see a
cases_test.go file in this exercise. This holds the test
cases used in the
leap_test.go. You can mostly ignore this file.
However, if you are interested… we sometimes generate the test data from a
cross language repository. In that repo
exercises may have a .json file that
contains common test data. Some of our local exercises have an
intermediary program that takes the problem specification
JSON and turns in into Go structs that are fed into the
file. The Go specific transformation of that data lives in the
To run the tests run the command
go test from within the exercise directory.
If the test suite contains benchmarks, you can run these with the
go test -v --bench . --benchmem
Keep in mind that each reviewer will run benchmarks on a different machine, with different specs, so the results from these benchmark tests may vary.
For more detailed information about the Go track, including how to get help if you’re having trouble, please visit the exercism.io Go language page.
JavaRanch Cattle Drive, exercise 3 http://www.javaranch.com/leap.jsp
It’s possible to submit an incomplete solution so you can see how others have completed the exercise.