Viktor Kleen

The problem is that the AFLplusplus makefiles only check whether `DEBUG` is set or not. But cargo always sets `DEBUG` to `true` or `false` and so convinces AFLplusplus to build...

The proposal looks good to me. The issues it discusses have bitten me regularly with the Terraform+Nickel project and it seems to me that metadata attached to fields together with...

So the issue is about having the existence of a record field depend on the values of other fields, possibly other fields defined far away via recursive record merging. Indeed,...

Since there continues to be interest in converting JSON schema and related specification into Nickel contracts, I've taken the liberty of updating @mtoohey31's first sketch to Nickel 1.0. I've also...

https://github.com/nickel-lang/json-schema-to-nickel should now be fully functional 🎉 It would certainly benefit from some stress testing, so please try it out!

I also prefer non-serialisable ADTs for now. The `export_with` metadata would only be sugar for calling a function on the ADT to produce a serialisable encoding, so this proposal shouldn't...

I'll take care of that later today, thanks for diagnosing!

Hmm, that's a tricky one. We needed it to make the static linking work, the binary wanted to link a few symbols from there. I'll need to take a deeper...

For reference, we could and maybe should follow [Unicode Standard Annex #31](https://www.unicode.org/reports/tr31/tr31-37.html) like [Rust](https://doc.rust-lang.org/reference/identifiers.html) itself is for identifiers.

That is indeed how `tf-ncl` works. The namespacing is an interesting concerns that I actually hadn't thought about yet. The other issue with the `output` field approach is that when...