There are many problems with window.Date so stop relying on it.

There are just a bunch of problems with relying on the JS Date representation that I do not think can be solved with the JS foundation. For example, the ISO 8601 parsing is impure for dates. It appears that elm-community/elm-time provides similar functionality, but in a pure way that takes the IANA time zone database into account. The pure approach could be improved with something like https://github.com/evancz/time-zone-database-proposal down the line. Unclear if we should stick with this choice, but I would like to explore alternatives first.
elm-lang · Jul 6, 2017 · a892fdf · a892fdf
1 parent fb79e28
commit a892fdf
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 317 deletions.
diff --git a/elm.json b/elm.json
@@ -10,7 +10,6 @@
         "Bitwise",
         "Char",
         "Color",
-        "Date",
         "Debug",
         "Dict",
         "Json.Decode",

diff --git a/src/Date.elm b/src/Date.elm
diff --git a/src/Elm/Kernel/Date.js b/src/Elm/Kernel/Date.js
diff --git a/src/Elm/Kernel/Debug.js b/src/Elm/Kernel/Debug.js
@@ -146,11 +146,6 @@ function _Debug_toString_dev(v)
 
 	if (type === 'object')
 	{
-		if (v instanceof Date)
-		{
-			return '<' + v.toString() + '>';
-		}
-
 		if (v.elm_web_socket)
 		{
 			return '<websocket>';