Yann Hamdaoui

Hey, thanks for asking! We are not there yet, but yes, the motivation of effects is precisely to be a generic way of implementing things like IFD in Nix, or...

It's actually a tricky question, because contracts are not predicates. It's a tad technical, but [this blog post](https://www.tweag.io/blog/2022-04-28-union-intersection-contracts/) touches upon the subject and how it makes it difficult to define...

You're right with respect to both points: - the predicate approach still forces values. The difference, I think, is that we don't need to have this `catch-like` mechanism in the...

> Nix already supports importing other languages, via the import-from-derivation feature. If the language can produce nix expressions in a derivation, nix will be able to `import` them as if...

> Nix is a pretty straightforward untyped lambda calculus, so in practice it’ll be at least as powerful once you erase all the nickel types. It might not be feasible...

A quick update: after more discussion with @edolstra, we are focusing on Kubernetes, with a handful precise examples in mind that we will convert to Nickel, and then try Nickel...

The motivation to use Nickel for Kubernetes is the same as for Dhall I guess: code reuse, documentation, modularity, and early failures (via both types and contracts), but with slightly...

I think Nickel has the potential to scale well, and scalability is in some form part of the design goals, e.g. we've been taking parallelizability into account when thinking about...

Revisiting this issue later, actually I think the issue and the fix, while related to instantiation, don't need to change when the instantiation is done. Rather, it seems that the...

> But `_a` _can unify with `b` Just to be sure, did you mean **can**, or **cannot** ?