Would <nested type aliases> (a feature that was co...
# functional
y
Would nested type aliases (a feature that was considered but scrapped for 1.1) be enough to implement higher-kinded types in Kotlin? It seemed like the reason they were scrapped is because it needed full-blown existential type support and it required having multiple "scopes" in a way. I'm not fully sure exactly if it would be possible to include that feature now, but if it was added, would that allow for HKTs?