Sultan

It is possible with a middleware, ex. ```js function plugin (context, block, line, column, id, length) { switch (context) { // executed whenever a block of css is done compiling....

It still does [Hydrate.js#L54](https://github.com/thysultan/dio.js/blob/master/experiment/src/Hydrate.js#L54), though this only works if you have an internal data structure to represent text nodes, [Element.js#L202](https://github.com/thysultan/dio.js/blob/master/experiment/src/Element.js#L202).

@mcjazzyfunky React supports iterators/iterables as children, how is React's implementation different from your suggestion? >trouble with iterators Can you post examples that post issues with iterators. On a secondary note...

>where does this information come from [A generator object is both iterator and iterable](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols#Is_a_generator_object_an_iterator_or_an_iterable) >even prevent certain advanced use cases Do you have any use cases in mind? I can...

>Anyway, even if not a real-world use case, I think it's not easily understandable why in the following That has nothing to do with generator functions and is solely related...

The issue(on the example posted) is not with generators/iterators but with the way react/dyo deals with shared/immutable virtual nodes, thus a separate issue and not a point of contention for/against...

Yes your right, i was mistaken on that point. i.e `[...aGeneratorObject[Symbol.iterator]()]` doesn't re-start it.

>Do I have to use keys here (like for other iterables You only need to use keys for computed children i.e `data.map(v => {v})` for example `[1, 2]` does not...

I have something like this working on next release of [Dyo](https://github.com/dyo/dyo/tree/hooks). The two things that allow this are: 1. the callback in `render(element, target, callback)` is always invoked after all...

@localvoid >Are you planning to rely just on suspense boundaries and promises? Yes suspense boundaries with [createResource/useResource](https://github.com/reactjs/rfcs/issues/106) are the perfect primitives that also avoid leaking into the global namespace, given...