The ndim allocation is less frequently used, the only place that it is needed I think was texture, and more recently there is a better way to special handle some of that through allocator interface itself.
Given builtins are only registered function rather than permanent data structures we can afford to iterate as need comes. My recommendation is start with allocator flat memory for now, then as need comes we add later. Let me know if that makes sense --- [Visit Topic](https://discuss.tvm.apache.org/t/memory-scope-for-vm-alloc-storage-builtins/15172/8) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/355a6581de5710dd96b8c6d9988c6c2f9dc2adb1f0f53d962345aa329645d0cf).
