You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem isn't the migration, it's the analysis phase who falsely gives the variable the state kind. If you look at the output in legacy mode you see that it creates a mutable source.
This enhances our "variable was mutated" detection to also recognize that `foo` in `[foo[1]] = [..]` was mutated. This allows us to be more granular about detecting mutations to each expressions in legacy mode, which fixes#12169
…roach) (#12429)
This enhances our "variable was mutated" detection to also recognize that `foo` in `[foo[1]] = [..]` was mutated. This allows us to be more granular about detecting mutations to each expressions in legacy mode, which fixes#12169
---------
Co-authored-by: Simon Holthausen <[email protected]>
Describe the bug
This...
...gets turned into this by the migrator:
There's no reason for this to be state.
Reproduction
demo
The text was updated successfully, but these errors were encountered: