Skip to content

Commit a0c9cd7

Browse files
nekevssjedel1043
andauthored
Update blog/2025-06-15-temporal-impl-1.md
Co-authored-by: José Julián Espina <[email protected]>
1 parent 844d653 commit a0c9cd7

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

blog/2025-06-15-temporal-impl-1.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -233,9 +233,9 @@ suspects `SystemTime` and `iana-time-zone`, merge it, and call it a day
233233
on the implementation, right?
234234

235235
Except the core purpose of `temporal_rs` is that it can be used in any
236-
engine implementation, accessing a system clock and system time zone are
237-
not in scope and must be left up to the engine or runtime to provide
238-
that functionality.
236+
engine implementation, and accessing a system clock and system time zone
237+
is sometimes difficult for engines that support targets like embedded systems.
238+
Thus, this functionality must be delegated to the engine or runtime ... somehow.
239239

240240
So how did we end up implementing Now if we have no access to the system
241241
clock or time zone? Well, a builder pattern of course!

0 commit comments

Comments
 (0)