Closed nikita-volkov closed 6 years ago
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
This particular thing seems to be caused by a mistake in the Json.Decode
implementation that was fixed elsewhere, but I am reading this as a feature request for code gen to produce code compatible with Closure Compiler. I think doing that makes sense, but I do not want to track requests in issues.
For some longer term perspective, I think we can do much better by analyzing things within Elm because we have so many more guarantees. The compiler can make more assumptions and be more aggressive. That said, compatibility with Closure Compiler will be a bit better in the next release.
Following is the error I get from Closure:
The version is: