google/ormolu
1
1
Fork 0
mirror of https://github.com/google/ormolu.git synced 2024-09-11 08:05:24 +03:00
Code Issues Projects Releases Wiki Activity

A couple more sentences about Brittany

Browse Source
This commit is contained in:
mrkkrp 2018-12-10 22:59:09 +07:00
parent b5e26f8b6f
commit bc2b919792
No known key found for this signature in database
GPG Key ID: 8564658B2889FF7C
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
DESIGN.md
View File

@ -334,6 +334,15 @@ straightforward:
more maintainable (IMO) and switching to that is equal to re-doing the
project.
In the end, design of Ormolu is going to be simpler and will:
* make the project more maintainable
* bugs easier to fix
* more people will be able to contribute to our project (I couldn't figure
out what is going on in Brittany, so I'd not be able to contribute, but
I could contribute to Hindent because I understand how it works even
though I spent equal amount of time looking at both)
* Forking or contributing to Hindent is not an option because if we replace
`haskell-src-exts` with `ghc` (or `ghc-exact-print`) then we'll have to
work with a different AST type and all the code in Hindent will become