Add setFunctionArgs lib function. #34466
Conversation
Among other things, this will allow *2nix tools to output plain data while still being composable with the traditional callPackage/.override interfaces.
|
Interesting bits are in trivial.nix |
|
I introduced a failure in the evaluator today, sorry about that. Testing for a fix: @GrahamcOfBorg eval |
|
This looks correct and whatnot, but I'm not sure I care about cabal2nix making plain data enough to warrant the extra complexity? I rather get rid of callPackage and its eta-expansion-hostile ways. |
|
I'd also like to use it for my soon-to-be-public setupcfg2nix. It's silly to produce a function from plain data, and we're not getting rid of callPackage any time soon as far as I know... |
There was a problem hiding this comment.
setFunctionArgs looks nice. I don't think that I'd use it in the Haskell infrastructure, though. Having access to plain data for those packages can be useful, but you can do that today already AFAIK.
I like the notion of simplifying access to plain data of those builds, but then I'd rather continue to explore NixOS/rfcs#3, which goes much farther than this approach.
Among other things, this will allow *2nix tools to output plain data
while still being composable with the traditional
callPackage/.override interfaces.