The language as it stands actually uses relatively little physical/committed memory, so could be used in embedded systems, but does rely on there being a 64-bit address space, which is probably still not as common in embedded.

I was going to ask the same, but I guess it may also not be good fit for some kernel programming, given that the heap is shared along with other code.

But sounds great for 64-bit user space, with enough (48-bit, or more) virtual addressing available. Obviously one can hit some snags if for some reason quite large allocations has to be done, but maybe one has to rethink that too.

I'm starting to fall in love with this approach ;)