Richard Feldman

What should happen if a line is over 80 characters and there is no syntactically valid way to get it under 80?

Hm, so if this can't get you an invariant (e.g. "set your terminal to 80 characters wide and everything will fit"), what's the benefit? Just that you don't have to...

What should happen in the case where you have a long thing that you'd want to break the other way? If it always breaks using the "argument on the same...

I think I've encountered it even more often with `exposing` - although in that case I'm often reluctant to manually split it. 😄

Let's keep exploring this. 😃 ## Long `exposing` lines causing merge conflicts [`Css.elm`](https://github.com/rtfeldman/elm-css/blob/0c83d527c401b49ac0c3481bfbdce7d25507b765/src/Css.elm) is often a fun pathological case when it comes to imports and file lengths, because that one...

Another thought: if `exposing` is auto-wrapped, it doesn't have to be "one per line" - it can be something like: ```elm module Foo exposing (bar, baz, qux, blah, something, somethingElse)...

The more I've used Prettier and `rustfmt`, which enforce line length, and `elm-format`, which doesn't, the more strongly I'm convinced that it's better not to enforce line length. Having now...

## Implications Currently the example in the issue is formatted like so: ``` decoder : Decoder User decoder = require "id" int require "email" string default "name" string "Guest" succeed...

> I'll open a pull request for review and I understand that you guys may decide not to merge it. I appreciate the attitude! ❤️ To summarize #210 from my...

Here are some points to add to the discussion: 1. Since the library came out, I have heard about the concern that people can swap arguments in decode pipeline and...