t; and I tend to compose them by building other shell scripts. I assume
> that is what you mean by pulling your hair out?
>
> Sometimes I also do composition by building Makefiles, which is kind of
> nice when you want to assemble many tasks that could possibly run in
> parallel.
>
>
uld possibly run in
parallel.
To have useful composition operators, wouldn't you need more precise
types for your IO actions?
Regards,
Rickard
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Not to turn this into a flame war, but there were discussions in the past
whether Nix should have been a DSL embedded in, say, Haskell. IIRC, you felt
okay about it being a standalone DSL, do you still feel the same way?
P.S. Yes, I know about Guix, but it's written in (a uni-typed) Scheme.
Hey Dan,
This sounds a lot like the motivation and design for nix-exec, have you
looked into whether it might work for you as-is or with something built
on top of it? I'd be happy to chat about this too if you want to go over
in more detail.
~Shea
Daniel Peebles writes:
Hi all,
I've been experimenting with a pattern recently that I'd say is fairly
close to a Haskell notion of IO. I have a collection of Nix-centered
scripts that need to perform fairly restricted side effects:
- Build an AMI (image) for AWS
- Write some disk image stuff to a raw device
-