Markus Laire

I just got an idea of how to fix this issue. Someone could create a package, called for example `InsaneString`, which mirrors `String` **exacly** and documents **properly** just how insane...

You don't understand the issue. I understand perfectly how floating point precision works. **Your example is incorrect because JS console doesn't show exact value but rounds it**. Here is correct...

> It looks like various languages disagree on how to do double to string conversions: > It might be wrong but then your issue isn't really with elm-format as much...

> A goal of elm-format is to format code canonically, such that it makes the actual behavior of the code more clear. Exactly my point. Value `18446744073709549568.0` stays **exactly same**...

> Can you show an example of some running code that demonstrates how the value is `18446744073709549568.0` and not `18446744073709550000.0` ? I already showed code which shows that `18446744073709550000.0` is...

@harrysarson Those bit values I showed above were 64-bit **integer** values, not `Float` values. As I've said `18446744073709550000.0` can't be represented as `Float` but is always converted to `18446744073709549568.0` so...

`` can't be used in Elm documentation because it's auto-escaped and rendered literally as text. (At least that's how `dmy/elm-doc-preview` renders it.) I actually tested that before making this bug...

It's just that whole `Internal`/`External` distinction becomes useless if I need to manually check the URL anyway. So if this can't be done in `Browser`, then `Internal`/`External` distinction should be...

> ... releases are already listed in the changelog, (hopefully) each one linking to the specific release page According to https://keepachangelog.com/ each release should link to comparison with previous version,...

I meant the example changelog there which shows how changelog should be formatted. It uses links like https://github.com/olivierlacan/keep-a-changelog/compare/v0.1.0...v0.2.0 for `0.2.0`.