ayazhafiz 4e942b3e5d Make nested datatypes into errors ... I was hoping to add nested datatypes into the language, but it turns out doing so is quite tricky and not all that useful with Roc's current compilation model. Basically every implementation strategy I could think of ended up requiring a uniform representation for the data layout (or some ugly workaround). Furhermore it increased the complexity of the checker/mono IR generator a little bit - basically, we must always pass around the alias definitions of nested datatypes and instantiate them at usage sites, rather than being able to unroll aliases as we currently do during canonicalization. So, especially because we don't support polymorphic recursion anyway, I think it may be better to simply disallow any kind of nested datatypes in the language. In any case, Stephanie Weirich [seems to think nested datatypes are not needed](https://www.cis.upenn.edu/~plclub/blog/2020-12-04-nested-datatypes/). Closes #2293		2022-01-31 22:58:01 -05:00
..
benches	Add simple benchmark for the parser: parse false-interpreter	2021-12-24 11:54:42 -08:00
fuzz	bump bumpalo	2021-04-18 14:36:47 +02:00
src	Make nested datatypes into errors	2022-01-31 22:58:01 -05:00
tests	Add parse tests for hosted modules	2022-01-30 20:40:50 -05:00
Cargo.toml	Add simple benchmark for the parser: parse false-interpreter	2021-12-24 11:54:42 -08:00