> The reason I was thinking about it was not actually anything to do with > garbage collection. I have a data modelling language with a type system, > but it has grown in a slightly ad-hoc manner and needs some > rationalization. I was wondering how well the type alias records + tagged > unions + basic types part of Elm would suit my purposes. As the data models > I build are often mapped onto relational database or mutable objects, I do > need circular references to be possible. >
I don't see the rationale for requiring circular references to map onto a relational database though, they are referenced by key, not by pointer. Mutable objects can of course use circular references, and some algorithms depend heavily on them, but they are a pain to handle for instance when serializing. Which you do a lot in a web app. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
