add DateTime module

[tim-smart]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: e4871d6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 31 packages

Name	Type
effect	Minor
@effect/schema	Major
@effect/cli	Major
@effect/cluster-browser	Major
@effect/cluster-node	Major
@effect/cluster-workflow	Major
@effect/cluster	Major
@effect/experimental	Major
@effect/opentelemetry	Major
@effect/platform-browser	Major
@effect/platform-bun	Major
@effect/platform-node-shared	Major
@effect/platform-node	Major
@effect/platform	Major
@effect/printer-ansi	Major
@effect/printer	Major
@effect/rpc-http	Major
@effect/rpc	Major
@effect/sql-d1	Major
@effect/sql-drizzle	Major
@effect/sql-kysely	Major
@effect/sql-mssql	Major
@effect/sql-mysql2	Major
@effect/sql-pg	Major
@effect/sql-sqlite-bun	Major
@effect/sql-sqlite-node	Major
@effect/sql-sqlite-react-native	Major
@effect/sql-sqlite-wasm	Major
@effect/sql	Major
@effect/typeclass	Major
@effect/vitest	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[johtso]

Exciting! Would you consider a type for representing a Date with no time component?

[tim-smart]

Exciting! Would you consider a type for representing a Date with no time component?

Maybe as a separate module in a new PR.

[fubhy]

Beautiful api design. Nice.

[fubhy]

One nitpick: I don't like the WithZone naming. The Temporal API uses ZonedDateTime. I think that has a better ring to it. Wdyt?

I'm wondering if we should align even more with the Temporal API suggestion and also use PlainDateTime for those without a timezone. But I'm not sure if I like that namechoice. But on the other hand it might make sense to preemptively align with that API.

[tim-smart]

One nitpick: I don't like the WithZone naming. The Temporal API uses ZonedDateTime. I think that has a better ring to it. Wdyt?

Trying out DateTime.Zoned, will see if it sticks :)

I'm wondering if we should align even more with the Temporal API suggestion and also use PlainDateTime for those without a timezone. But I'm not sure if I like that namechoice. But on the other hand it might make sense to preemptively align with that API.

I'll stick with Utc, as technically this isn't a plain date time as it wraps a epoch timestamp.

[fubhy]

Trying out DateTime.Zoned, will see if it sticks :)

Sounds much better imho. Especially in the onUtc vs. onZoned matcher. :-)

[fubhy]

Hot.