google/ormolu
1
1
Fork 0
mirror of https://github.com/google/ormolu.git synced 2024-11-23 14:16:24 +03:00
Code Issues Projects Releases Wiki Activity
4bed990334
ormolu/default.nix

83 lines
1.8 KiB
Nix
Raw Normal View History

Adjust the nix expression to facilitate importing from outside
2019-08-16 13:02:00 +03:00
{ pkgs ? (import ./nix/nixpkgs) }:
Clean nix configuration * Point to more recent nixpkgs commit. This fixes build issue with python 3.7.3 (only on darwin?). * Separate shell.nix and default.nix. This is so that lorri can be used for development. * Add nix output to .gitignore. * Format *.nix using nixfmt. * Use gitignore for filtering files in nix derivation.
2019-06-19 23:48:47 +03:00
let
Use GHC 8.6.5
2019-08-28 15:15:35 +03:00
ormoluCompiler = "ghc865";
Add nix expression for reformatting sources of arbitrary packages See the description in readme.
2019-07-14 02:01:02 +03:00
source = pkgs.lib.sourceByRegex ./.[
"^.*\.md$"
"^app.*$"
"^data.*$"
"^ormolu.cabal$"
"^src.*$"
"^tests.*$"
];
Adjust the nix expression to facilitate importing from outside
2019-08-16 13:02:00 +03:00
haskellPackages = pkgs.haskell.packages.${ormoluCompiler}.override {
overrides = ormoluOverlay;
Clean nix configuration * Point to more recent nixpkgs commit. This fixes build issue with python 3.7.3 (only on darwin?). * Separate shell.nix and default.nix. This is so that lorri can be used for development. * Add nix output to .gitignore. * Format *.nix using nixfmt. * Use gitignore for filtering files in nix derivation.
2019-06-19 23:48:47 +03:00
};
Adjust the nix expression to facilitate importing from outside
2019-08-16 13:02:00 +03:00
ormoluOverlay = self: super: {
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
"ormolu" = super.callCabal2nix "ormolu" source { };
};
Add nix expression for reformatting sources of arbitrary packages See the description in readme.
2019-07-14 02:01:02 +03:00
ormolize = import ./nix/ormolize {
inherit pkgs;
inherit haskellPackages;
};
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
ormolizedPackages = doCheck:
pkgs.lib.mapAttrs (_: v: ormolize { package = v; inherit doCheck; }) haskellPackages;
Clean nix configuration * Point to more recent nixpkgs commit. This fixes build issue with python 3.7.3 (only on darwin?). * Separate shell.nix and default.nix. This is so that lorri can be used for development. * Add nix output to .gitignore. * Format *.nix using nixfmt. * Use gitignore for filtering files in nix derivation.
2019-06-19 23:48:47 +03:00
in {
ormolu = haskellPackages.ormolu;
Adjust the nix expression to facilitate importing from outside
2019-08-16 13:02:00 +03:00
ormoluShell = haskellPackages.shellFor {
Clean nix configuration * Point to more recent nixpkgs commit. This fixes build issue with python 3.7.3 (only on darwin?). * Separate shell.nix and default.nix. This is so that lorri can be used for development. * Add nix output to .gitignore. * Format *.nix using nixfmt. * Use gitignore for filtering files in nix derivation.
2019-06-19 23:48:47 +03:00
packages = ps: [ ps.ormolu ];
Change the way operators are formatted
2019-08-06 14:29:50 +03:00
buildInputs = [ haskellPackages.cabal-install haskellPackages.ghcid ];
Clean nix configuration * Point to more recent nixpkgs commit. This fixes build issue with python 3.7.3 (only on darwin?). * Separate shell.nix and default.nix. This is so that lorri can be used for development. * Add nix output to .gitignore. * Format *.nix using nixfmt. * Use gitignore for filtering files in nix derivation.
2019-06-19 23:48:47 +03:00
};
Adjust the nix expression to facilitate importing from outside
2019-08-16 13:02:00 +03:00
inherit ormoluOverlay ormoluCompiler;
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
hackage = ormolizedPackages false;
hackageTests = with pkgs.lib; pkgs.recurseIntoAttrs (
let ps = [
"QuickCheck"
"ShellCheck"
"aeson"
"attoparsec"
Refactor the comment rendering code and ‘newline’ This removes (or rather puts it to a lower level) logic around “modifying newline” because it was very hard to reason about and almost blocked my work on fixing issue #337. I also dropped debugging output because it's too verbose and I'm not using it anyway. As part of these changes I also changed now the ‘newline’ combinator works. Now, similar to ‘space’, the second ‘newline’ in a row just tells the rendering engine to prefix next thing with a newline, using the ‘newline’ combinator more than twice in a row has no effect. To take full advantage of the new feature I also went through the code and simplified some logic around outputting exact amount of newlines because now it's harder to get things wrong, so we can be less careful with counting newlines.
2019-09-04 13:05:48 +03:00
"aws"
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
"cassava"
"conduit"
"cryptonite"
"diagrams-core"
"distributed-process"
"esqueleto"
"fay"
Refactor the comment rendering code and ‘newline’ This removes (or rather puts it to a lower level) logic around “modifying newline” because it was very hard to reason about and almost blocked my work on fixing issue #337. I also dropped debugging output because it's too verbose and I'm not using it anyway. As part of these changes I also changed now the ‘newline’ combinator works. Now, similar to ‘space’, the second ‘newline’ in a row just tells the rendering engine to prefix next thing with a newline, using the ‘newline’ combinator more than twice in a row has no effect. To take full advantage of the new feature I also went through the code and simplified some logic around outputting exact amount of newlines because now it's harder to get things wrong, so we can be less careful with counting newlines.
2019-09-04 13:05:48 +03:00
"haxl"
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
"hedgehog"
"hlint"
"megaparsec"
Refactor the comment rendering code and ‘newline’ This removes (or rather puts it to a lower level) logic around “modifying newline” because it was very hard to reason about and almost blocked my work on fixing issue #337. I also dropped debugging output because it's too verbose and I'm not using it anyway. As part of these changes I also changed now the ‘newline’ combinator works. Now, similar to ‘space’, the second ‘newline’ in a row just tells the rendering engine to prefix next thing with a newline, using the ‘newline’ combinator more than twice in a row has no effect. To take full advantage of the new feature I also went through the code and simplified some logic around outputting exact amount of newlines because now it's harder to get things wrong, so we can be less careful with counting newlines.
2019-09-04 13:05:48 +03:00
"ormolu"
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
"postgrest"
"servant"
"servant-server"
"tensorflow"
Handle operator chains better I implemented a custom logic where we assign a score to every occurance of an operator based on their location, and the average of that score determine the fixity of the operator. As you can imagine, the solution is a bit brittle; and it is easy to mislead it if you knowingly craft an input, but it gave acceptable results for every code snippet I found online. And since it returns the same AST no matter how we infer the fixities, it is not the end of the world if we infer something incorrectly. The code is not really optimised, and I think it has quadratic time complexity. Notably, we use opTreeLoc function quite often and it traverses the whole tree every time. Memoizing that on the OpBranch constructor would make formatting files with reeeally long operator chains a lot faster. We can do this once we decide to optimize for speed.
2019-09-04 09:33:58 +03:00
"text_1_2_4_0"
Enable checking the ‘tls’ package on CI
2019-09-06 20:22:15 +03:00
"tls"
Refactor the comment rendering code and ‘newline’ This removes (or rather puts it to a lower level) logic around “modifying newline” because it was very hard to reason about and almost blocked my work on fixing issue #337. I also dropped debugging output because it's too verbose and I'm not using it anyway. As part of these changes I also changed now the ‘newline’ combinator works. Now, similar to ‘space’, the second ‘newline’ in a row just tells the rendering engine to prefix next thing with a newline, using the ‘newline’ combinator more than twice in a row has no effect. To take full advantage of the new feature I also went through the code and simplified some logic around outputting exact amount of newlines because now it's harder to get things wrong, so we can be less careful with counting newlines.
2019-09-04 13:05:48 +03:00
"yesod-core"
Test a few Hackage packages on CI
2019-08-30 05:43:38 +03:00
# Comment idempotence issue
# "Agda"
# "brick"
# "hakyll"
# "hledger"
# "http-client"
# "idris"
# "intero"
# "leksah"
# "pandoc"
# "pipes"
# "stack"
# Missing language extension
# "lens" #fixed in master
# "purescript"
];
in listToAttrs (map (p: nameValuePair p (ormolizedPackages true).${p}) ps)
);
Clean nix configuration * Point to more recent nixpkgs commit. This fixes build issue with python 3.7.3 (only on darwin?). * Separate shell.nix and default.nix. This is so that lorri can be used for development. * Add nix output to .gitignore. * Format *.nix using nixfmt. * Use gitignore for filtering files in nix derivation.
2019-06-19 23:48:47 +03:00
}
Reference in New Issue Copy Permalink