Skip to content

Leap

Decide whether a year is a leap year in the Gregorian calendar.

Adapted from Exercism’s problem specification (MIT). Listed under Dates & Time.

// FILE: leap.nomi
//# Leap years in the Gregorian calendar.

import std::calendar.Date

/// Whether `year` is a leap year in the Gregorian calendar.
pub fn is_leap_year(year: Int) -> Bool
    Date.is_leap_year(year)
end

// FILE: leap_test.nomi
import leap.is_leap_year

test "leap years"
    [
        ("year not divisible by 4 in common year",                      2015, False),
        ("year divisible by 2, not divisible by 4 in common year",      1970, False),
        ("year divisible by 4, not divisible by 100 in leap year",      1996, True),
        ("year divisible by 4 and 5 is still a leap year",              1960, True),
        ("year divisible by 100, not divisible by 400 in common year",  2100, False),
        ("year divisible by 100 but not by 3 is still not a leap year", 1900, False),
        ("year divisible by 400 is leap year",                          2000, True),
        ("year divisible by 400 but not by 125 is still a leap year",   2400, True),
        ("year divisible by 200, not divisible by 400 in common year",  1800, False),
    ]
    |> subtests (description, year, expected), description
        assert is_leap_year(year) == expected
    end
end
  • The answer is std/calendar’s Date.is_leap_year, which holds the rule (year % 4 == 0 and (year % 100 != 0 or year % 400 == 0)), so the solution does not write it again. Python’s solution can call calendar.isleap the same way.
  • The function is is_leap_year: a predicate of a state takes is_ (style §4), and std’s own is named the same.
  • The cases are one subtests table. Each row’s first column is the canonical description, which names the row (subtests cases, (description, year, expected), description), so a failed row’s report shows which case it was.