Skip to content

Commit 7497ff4

Browse files
Update proposed/clock-meta.md
Co-authored-by: Alexander Makarov <[email protected]>
1 parent d366693 commit 7497ff4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

proposed/clock-meta.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ be enforced on the language level is, that the returned value is of type `DateTi
150150
currently is no way to enforce that this object has a certain timezone as its value. So from a language
151151
level perspective there is no way to explicitly enforce a certain timezone in the returned object.
152152

153-
On the other hand there is also a logical reason. The explicit contract should be usable in all situations
153+
On the other hand, there is also a logical reason. The explicit contract should be usable in all situations
154154
where one needs a way to retrieve the current time. And on the contract level we should not make an
155155
assumption about what the caller might need. So would the contract define that only UTC is returned, then
156156
use-cases that do require something else will have to explicitly work around that or find other ways of

0 commit comments

Comments
 (0)