Chayim Refael Friedman 61f162a43d Handle destructuring assignments uniformly ... Instead of lowering them to `<expr> = <expr>`, then hacking on-demand to resolve them, we lower them to `<pat> = <expr>`, and use the pattern infrastructure to handle them. It turns out, destructuring assignments are surprisingly similar to pattern bindings, and so only minor modifications are needed. This fixes few bugs that arose because of the non-uniform handling (for example, MIR lowering not handling slice and record patterns, and closure capture calculation not handling destructuring assignments at all), and furthermore, guarantees we won't have such bugs in the future, since the programmer will always have to explicitly handle `Expr::Assignment`. Tests don't pass yet; that's because the generated patterns do not exist in the source map. The next commit will fix that.		2024-10-20 19:09:51 +03:00
..
src	Handle destructuring assignments uniformly	2024-10-20 19:09:51 +03:00
Cargo.toml	Replace once_cell with std's recently stabilized OnceCell/Lock and LazyCell/Lock	2024-08-16 09:53:37 +03:00