Re: [Haskell-community] Standard package file format

On 17 September 2016 at 03:43, Herbert Valerio Riedel wrote: > > I'm not sure if this has been pointed out already, but beyond turning a > proper grammar into a stringly-typed one, shoehorning some features of > .cabal files into YAML syntax really appear like a case of the

Re: [Haskell-community] [Haskell-cafe] Standard package file format

On 16 September 2016 at 16:51, Paolo Giarrusso wrote: > > I agree "full-fledged build system" is not a possible immediate goal. > But an EDSL for expressing cabal projects (as they are today) would > still be in scope of your proposal—and I thought you liked the idea >

Re: [Haskell-community] [Haskell-cafe] Standard package file format

On 16 September 2016 at 12:35, Imants Cekusins wrote: > Why not adopt (a subset of) .hs AST file format to structure both project > and package files? > Aha, that's my preferred choice. If there is a way to restrict features and we can allow just a subset we can have a nice

[Haskell-community] Standard package file format

I am starting a new thread for the package file format related discussion. >From a developer's perspective, the major benefit of a standard and widely adopted format and is that people can utilize their knowledge acquired from elsewhere, they do not have to go through and learn differently

Re: [Haskell-community] [Haskell-cafe] technical thoughts on stack

There are multiple ways to achieve this: 1) The env command being discussed is actually "stack exec env". Though it includes the full environment rather than stack exclusive. You can use "stack path" to print the stack exclusive environment. You can also use "stack path --" to pick specific items