Sebastian Markbåge
Sebastian Markbåge
Note that even `` doesn't need a dependency on `react-dom` since it can render the tag as a string and the ref resolves directly to the node.
Yea this probably breaks without it. https://github.com/reactjs/react-art/blob/master/src/ReactART.js#L198
@spicyj Not if that composite was rendered by a different renderer than `react-dom`. Unless it also uses the same `ReactInstanceMap`. Note that this is the Surface so it shouldn't have...
@dai-shi You can call async functions and use their Promises. It's the same principle for why async functions are annotated and have `await`.
Yea, no that's a limitation. They have to be Hooks or you have to read it on the outside and pass it in. If Hooks could be made conditional and...
It's not quite that easy it turns out. Added a bunch of TODOs.
There's no way to silence the logs when an error boundary catches it now but I have a follow up to change a few other things and introduce a possible...
To phrase it differently `return`, `continue` and `break` are all the same in that you're not allowed to use them to escape the do-expression. The only thing special about `return`...
> Is there precedent for disallowing return/continue/break in other languages with expression logic like this? Rust has a different semantic than what @syranide expected and thought was the more useful...
I'm getting more convinced that `for` returning an array is not the right way. The argument for comprehensions is usually to make it easy to write in a functional compositional...