G. Allais 937aa8fc43 [ refactor ] introducing Namespace (#638) ... Until now namespaces were stored as (reversed) lists of strings. It led to: * confusing code where we work on the underlying representation of namespaces rather than say what we mean (using `isSuffixOf` to mean `isParentOf`) * potentially introducing errors by not respecting the invariant cf. bug report #616 (but also name generation in the scheme backend although that did not lead to bugs as it was self-consistent AFAICT) * ad-hoc code to circumvent overlapping interface implementation when showing / pretty-printing namespaces This PR introduces a `Namespace` newtype containing a list of strings. Nested namespaces are still stored in reverse order but the exposed interface aims to support programming by saying what we mean (`isParentOf`, `isApproximationOf`, `X <.> Y` computes to `X.Y`, etc.) irrespective of the underlying representation.		2020-09-05 09:41:31 +01:00
..
TT.idr	[ refactor ] introducing Namespace (#638)	2020-09-05 09:41:31 +01:00
TTImp.idr	Fix MkRecord signature	2020-06-11 21:54:40 +02:00