Thanks for the interesting discussion.
@tqchen @junrushao1994 ,
In terms of the definition of the target, I see two categories of arguments
presented here :
C1 : The executor, runtime, should belong to the target -- even if means
duplication.
C2 : The targets should be hierarchical and re
Thanks @manupa-arm , building on what you said.
- I do not think there is a strong contention on C1, the main point is that the
target can be recursive. So a target like the follows is totally OK.
```bash
- kind: hetro-exec
- runtime : crt
- executor: vm
- devices: [ se_scope0, se_scope1 ]
``
Oh wow, I've been away for a few days and really appreciate the amount of
discussion that's arrived :smile_cat: Thanks @mbs-octoml, @zxybazh, @tqchen,
@comaniac, @junrushao1994 and @manupa-arm!
Firstly let's address a few specifics which may help narrow the discussion
slightly:
[quote="junru
To elaborate on C2, while it is desirable and recommended to have consolidated
runtime, executor choice when possible. Naturally there are cases that would
requires a bit of generalization. The multi-machine case is one example.
There are also other examples that can appear on a single SoC. C
Following a video chat discussion with @vinx13 , we touched on a number of
points, summarized below. Also, we are adding @vinx13 as a co-author on this
RFC.
- Are there cases where the flattening in `StorageFlatten`/`FlattenBuffer`
should be inferred from buffer properties, rather than explici
