# \#calendar

**URL:** https://forums.swift.org/tag/calendar/931.md

[Latest](https://forums.swift.org/latest.md) · [Categories](https://forums.swift.org/categories.md) · [Tags](https://forums.swift.org/tags.md)

---

## [Calendar nextDate/enumerateDates provides wrong dates](https://forums.swift.org/t/calendar-nextdate-enumeratedates-provides-wrong-dates/68943)

<div class="topic-metadata">

**Author:** [@alpennec](https://forums.swift.org/u/alpennec)\
**Replies:** 10\
**Last updated:** [October 13, 2026, 1:35pm UTC](https://forums.swift.org/t/calendar-nextdate-enumeratedates-provides-wrong-dates/68943 "2026-10-13T13:35:30Z")

</div>

I’m trying to get previous dates that matches specific months in the year. It mainly works but for an unknown reason, it does not work as expected for the 9nth month in the Gregorian calendar (which is September). When t…

---

## [Expressively initialising calendars for specific time zones](https://forums.swift.org/t/expressively-initialising-calendars-for-specific-time-zones/86139)

<div class="topic-metadata">

**Author:** [@kiel](https://forums.swift.org/u/kiel)\
**Replies:** 19\
**Last updated:** [May 4, 2026, 2:10am UTC](https://forums.swift.org/t/expressively-initialising-calendars-for-specific-time-zones/86139 "2026-05-04T02:10:12Z")

</div>

Presently, if we want a Calendar object configured with a specific time zone, we have to write this: let sydney = TimeZone(identifier: "Australia/Sydney")! var calendar = Calendar(identifier: .gregorian) calendar.timeZo…

---

## [DayType — A Swift API for dates without the time baggage](https://forums.swift.org/t/daytype-a-swift-api-for-dates-without-the-time-baggage/85747)

<div class="topic-metadata">

**Author:** [@Drekka](https://forums.swift.org/u/Drekka)\
**Replies:** 12\
**Last updated:** [April 3, 2026, 8:29am UTC](https://forums.swift.org/t/daytype-a-swift-api-for-dates-without-the-time-baggage/85747 "2026-04-03T08:29:31Z")

</div>

Hello everyone, I'd like to share a package I've been working on called DayType. The problem DayType solves Swift's Date APIs are great, but they are also limited by their focus on representing points in time. This me…

---

## [repeatedTimePolicy parameter of Calendar.nextDate not working when matching nanoseconds?](https://forums.swift.org/t/repeatedtimepolicy-parameter-of-calendar-nextdate-not-working-when-matching-nanoseconds/82300)

<div class="topic-metadata">

**Author:** [@Serika\_PHB](https://forums.swift.org/u/Serika_PHB)\
**Replies:** 1\
**Last updated:** [September 23, 2025, 10:54pm UTC](https://forums.swift.org/t/repeatedtimepolicy-parameter-of-calendar-nextdate-not-working-when-matching-nanoseconds/82300 "2025-09-23T22:54:57Z")

</div>

Because of the transition from PDT to PST, there will be two 1:30 in 2/11/2025, which can be distinguished with the repeatedTimePolicy parameter when calling Calendar.nextDate. var calendar = Calendar.init(identifier: .…