Yann Hamdaoui

Closing in favor of #418. Note that a JSON schema to Nickel contract converter is to be worked on by @vkleen soon.

Closing as this is solved by `std.contract.Sequence`. There are interesting side ideas and questions here, but I think they will be better tracked and considered as separate issues. I think...

> I would really like to not introduce yet another locking+caching mechanism for dependencies. I wholeheartedly agree. > In the syntax example above I use scheme:package as source definition. Here...

> Defaulting to Nix has its downsides: not everybody wants to or can use Nix. It would be a shame if Nickel wouldn't work on Windows just because it requires...

This is an old issue, but I think the recent machinery of Nickel could alleviate the original issue without introducing either nominal typing or named contract. ## Values don't have...

@digitalmoksha thanks for your input. Indeed, this is what I ended up doing - wrapping every list item in a paragraph. I guess my point is that it's not obvious...

Thanks for the elaborate and considerate answer @kivikakk. I might have got confused by reading the AST definition, I thought `custom_block` was actually allowing inline elements to be part of...

> It's a little more complicated than that. The node types you see in the nodes module don't actually carry the tree structure; they're provided by arena_tree, which doesn't know...

I would like to make sure that I understand the semantics precisely. In your example, you already know that you need a `bar` field to be defined somewhere, that's why...

It seems that what you want, in the end, is to apply a contract to the fragment: ```nickel { name = "foo", buildScript = "echo $MESSAGE > $out", env.MESSAGE =...