"snack shell" capability?

[feuerligin]

I could alternatively have a deps.nix with a list of deps that would be passed to a ghcWithPackages for shell.nix and to the dependencies = field in snack.nix, but could this be made easier?

[nmattia]

That's a good question, and I'm assuming that if you have some extra system library dependencies (when there's support for it in Snack) you'd also like them to show up in the shell? What else, besides ghc, do you think should be in that shell?

[langston-barrett]

@nmattia The best approach would probably be to have the user create a shell.nix of some specified format that lists whatever they'd like to have in the shell, e.g.

{ pkgs }:
with pkgs; {
  someShellConfigOption = true;
  additionalPackages = [ haskellPackages.hlint ];
}

[masaeedu]

Sorry if this is off topic here, but would something like a snack shell workflow be necessary to provide the necessary GHC, devtools, etc. to an editor? Or is there some other, already existing mechanism for making hdevtools work with snack?