> Compact regions, allowing better control over garbage collection in the presence of large heaps containing many long-lived objects.<p>Can someone explain how this feature works and/or how much impact it has on Haskell's feasibility as a performant, i.e., game engine or real-time application language?
> A new, more type-safe type reflection mechanism<p>Does this mean GHC does not erase types at runtime? Or perhaps what do they mean by "reflection" here; I only know it in the context of Java, where it more or less felt like an anti-pattern.