Josh Story
Josh Story
closing in favor of https://github.com/facebook/react/pull/29491
@dantman Interesting idea for sure. I think the way context is currently implemented internally would make some of the really dynamic stuff hard but the static stuff could probably be...
@PedroBern thanks for your input I think your advice here is useful for a certain kind of optimization, even a very common one, however it does not address the main...
@sebmarkbage >One general optimization we could do is to eagerly call the render function during propagation and see if the render yields a different result and only if it does...
>The main problem that happens in practice is that we end up rendering beyond the component reading the Context because that component creates a new object (e.g. JSX element) that...
@sebmarkbage are there established methods to test upper and lower bounds across sync and concurrent modes? I found this part of testing #118 very hard because I had to contrive...
@josephsavona Unfortunately TS is not very sound. (nor is flow in some cases like with array access) and so if you use the Record type you can get into a...
Yeah what I meant by unsound is that reading from a Record can return undefined at runtime but the type system doesn't model this (except in TS if you use...
@souporserious we had an error in our docs. the `precedence` value is arbitrary and can be anything. React infers no special meaning from the value used but instead just assumes...
Fixing docs here: https://github.com/reactjs/react.dev/pull/6908