By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Read a Maybe of a primitive, and not a collection of one A collection of a thing has a different character from the thing: a reader of a list has been told that there are several, which is something, and the name it wants goes on the element rather than on the field. A Maybe holds at most one, so a field holding one is as anonymous as a field holding the thing, and the newtype that fixes it goes inside. [Char] stays, because it is String spelled out and a primitive read under one spelling and not the other would be a way around the rule that nothing else closes. Which containers are transparent leaves Facts.Primitive with this, because the two rules that share its list of primitives want different answers and both are right: one asks whether a field holds an anonymous primitive, where a collection is not the thing, and the other asks where a newtype would go, where it goes inside the collection. The shared module says so and each rule answers for itself. What this costs is the shape of all three sites the rule found in this repository, each of which held its only primitive as a list. They have their types now, and the rule will not ask for the next one.