Joe Savona 65c54e2d70 Repro for unmemoized array due to mutation surrounding hook ...

Distilled repro of an internal example we found. Forget determines a mutable 
range for the array, but that mutable range spans a hook call, so the reactive 
scope gets pruned. That's all working as expected. 

What isn't ideal though is that if we know `x` is an array and `f` can't mutate 
its arguments, then `x.map(f)` shouldn't count as a mutation of `x`, since 
Array.prototype.map can only mutate the receiver via the callback (if the 
callback mutates its args). 

Improving on this example requires a) we have to know it's an Array, via type 
information or bc we saw an array literal and b) being precise about which 
functions could possibly mutate their parameters, which is tricky because of 
indirect mutations via stores, etc.

2023-11-29 10:46:42 -08:00

compiler

Repro for unmemoized array due to mutation surrounding hook

2023-11-29 10:46:42 -08:00

S

Description

No description provided

declarativefrontendjavascriptlibraryreactui

MIT 1.8 GiB

Languages

JavaScript 67.1%

TypeScript 29.4%

HTML 1.5%

CSS 1.1%

C++ 0.6%

Other 0.2%