If closures causing "hidden" allocations is problematic, from a language-design perspective, then it's...

...GC allocation. My point is that GC allocations shouldn't cause errors/warnings outside of...

I see no point in having closure allocations causing compiler warnings. That's what profilers...

...because well, it's immutable.  But once allocations are bound to a thread, this sharing...

...discussed language guarantees would make sure your allocations are not mixed or illegally referenced across...

...use per-thread heaps?

I.e. all allocations would need to be per thread, and...

...logic, the compiler sometimes turns GC allocations into stack allocations too eagerly. Here I got...

...decide to call the GC if the allocations have been high enough.

This would allow...

...embedded systems about disabling of dynamic memory allocations.
* Phobos support isn't ready for now...

...Teoh

void main() @nogc
{
    // Look, ma! No allocations!
    int[3] arr = v[1,2,3...