Closed lue-bird closed 12 months ago
This also changes
a
|> f
|> Tuple.pair g
-->
( g,
a
|> f
)
which I don't think we want in this specific instance. Pipelining (and partial application) is almost the only "valid" uses I see/have for Tuple.pair
.
Not handling this should make the fix much simpler too
To complete the suggested tuple simplifications from #2
It's pretty easy to mess indentation up with these fixes that use
extractSourceCode
, so the fix preserves it 1:1.I'm not really sure about the error details on this one. Why is the code obviously better after the simplification?