New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leading arrows #95
Leading arrows #95
Conversation
TODO
- bar ::
- String ->
- String ->
- a
+ bar
+ :: String
+ -> String
+ -> a Putting GADTs sometimes look weird. Should data/examples/declaration/value/function/typed-expressions-four-out.hs have an indented in: foo x = x::Int
bar x = Just x ::
Maybe String out: foo x = x :: Int
bar x =
Just x
:: Maybe String |
3f77e03
to
294872a
Compare
294872a
to
30e5e59
Compare
OK, I've fixed the GADT weirdness, for some reason in Ormolu the existing rendering for GADTs duplicated lots of work from p_hsType |
Upstream PR for some changes: https://github.com/tweag/ormolu/pull/711/files |
You're awesome and your dog is awesome! |
If I were to fix the merge conflicts would it stand a chance of getting merged? I think it's quite a sought after feature. |
It would be merged right away into our fourmolu fork (fourfourmolu? sixteenmolu?). |
Hey. What is the status of this PR? It would be great to have this in fourmolu as "hanging arrows" is not the style I've seen anyone use when writing code without a formatter. |
Probably depends on #49 |
d85cd0c
to
3a667cc
Compare
c7364ed
to
40bcc74
Compare
👋 @expipiplus1 If you haven't noticed, we finally merged in a new testing framework for configuration options (#169)! This means we can finally address the backlog of open PRs. Please do the following steps
You can use #135 as a reference for this checklist. |
I did see that! Very exciting.
No chance I'll be able to get to this before July, but I'm happy for
someone else to take over before then. I'll hopefully find time in July or
later otherwise.
…On Wed, Jun 1, 2022 at 12:59 PM Brandon Chinn ***@***.***> wrote:
👋 @expipiplus1 <https://github.com/expipiplus1>
Thank you for opening this PR and being patient while we sorted out how to
handle all the new contributions for new configuration options!
If you haven't noticed, we finally merged in a new testing framework for
configuration options (#169
<#169>)! This means we can
finally address the backlog of open PRs.
Please do the following steps
-
Rebase against main
git remote add upstream ***@***.***:fourmolu/fourmolu
git fetch upstream
git rebase -i upstream/main
-
Resolve merge conflicts
-
Ensure CHANGELOG.md has been updated
-
Ensure configuration docs in README.md have been updated
-
Ensure fourmolu.yaml updated to stay in sync with config in README.md
-
Ensure tests have been added
You can use #135 <#135> as a
reference for this checklist.
—
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGRJXCVWLSQSWGRMOR75ATVM3U2LANCNFSM46SVXTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@expipiplus1 I can try rebasing your branch and adding tests if you don't mind. |
That would be great :)
…On Mon, 20 Jun 2022, 8:13 pm Kyriakos Papachrysanthou, < ***@***.***> wrote:
@expipiplus1 <https://github.com/expipiplus1> I can try rebasing your
branch and adding tests if you don't mind.
—
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGRJXDLY2LVIXX5235CMN3VQC7D3ANCNFSM46SVXTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Closing in favor of #209 |
This adds a --leading-arrows option and closes #86
It's currently on top of my alignment branch for my convenience, I don'tthink it should be that hard to extract though
I've extracted it from on top of my align work, although it's a more convenient for me to have it on there. I'll be keeping that up to date on this branch (joe-align-leading) https://github.com/expipiplus1/fourmolu/tree/joe-align-leading
CC @dpwiz