tazjin / yants Goto Github PK

I find the nesting of eithers annoying to write, and inconsequential. As a result, there should probably be a one-of sort of type constructor, s.t. oneof [a b c] either computes to either<a,either<b,c>>, or be its own type that behaves as such.

You might want to call it union, or you might want to avoid such language! :)

The current struct system checks for both the presence of mandatory fields, and the absence of extraneous fields.

There is some granularity offered in having optional fields, but it is sometimes useful to have more fine-grained control, such as:

Open structures
Where mandatory fields are checked for presence, but extraneous fields are fine.

Intersection types
In the presence of open structures, it starts making sense to ask for a value to have several types at once.

This could be quite a bit of work, so I understand if it takes a while to think through and decide whether to add them!

All your examples assume that the library is already in scope.

Are you just supposed to:

with (import /path/to/yants/default.nix {});
... 

?