Changing RawSpec/SpecValue

[Laar]

The current implementation for the combined function and enum types is getting out of hand. For each mapping (Location, Definition, etc.) using SpecValues or ValueNames two functions need to be added to SpecValue. While the current design is simple and usable it does not scale well if more mappings are added. Thus something better is needed.

A better design would probably be to add something like

data BiMap f = BiMap (f EnumValue) (f FuncValue)

and using this to recreate the current mappings (using newtypes). Furthermore the addition of data Bi b = Bi b b (or something like that) could improve some double values (like the reuses filepaths), and possibly reduce the number of explicit type signatures.

[Laar]

I tried implementing a pair of values one for EnumValue and one for FuncValue (so apart from the machinery and interpretation isomorphic to (a,a) for a given a). Though my main use-case for it, simplifying the pair of filepaths for reuses, didn't work. The problem is that it creates a cyclic dependency. To define SpecValue the options type is needed, which uses this new value type for the reuses files. But the new value type need needs SpecValue to differentiate between enums and functions completing the cycle.

Removing the dependency of SpecValue on the options would fix this and it is (I think) the only link that can really be broken. The disadvantage would be that the conversion of names would need to be done outside of Spec.Base, which breaks the abstraction/safety. Therefore I'm starting to wonder if adding this special pair is worth the trouble.