Can I destructure a tuple without binding the result to a new variable in a let/match/for statement?

by

No.

Destructuring is something you can only do with patterns; the left-hand side of an assignment is not a pattern, hence you can’t destructure-and-assign.

See proto-RFC 372 (Destructuring assignment) which discusses the possibility of adding this feature.

More Related Contents:

  1. Why do I need to import a trait to use the methods it defines for a type?
  2. Should trait bounds be duplicated in struct and impl?
  3. How do I collect into an array?
  4. Can I do type introspection with trait objects and then downcast it?
  5. Cannot borrow as mutable more than once at a time in one code – but can in another very similar
  6. How can I perform parallel asynchronous HTTP GET requests with reqwest?
  7. Is it considered a bad practice to implement Deref for newtypes?
  8. Implementing a trait for multiple types at once
  9. Convert a String to int?
  10. How do I get an owned value out of a `Box`?
  11. How do I borrow a RefCell, find a key, and return a reference to the result? [duplicate]
  12. Converting from Option to Option
  13. Trait implementation for both a trait object and for direct implementors of the trait
  14. Can’t borrow mutably within two different closures in the same scope
  15. Why does my variable not live long enough?
  16. How to iterate over and filter an array?
  17. If BufReader takes ownership of a stream, how can I read and write lines on it?
  18. How to fix lifetime error when function returns a serde Deserialize type?
  19. Is there another option to share an Arc in multiple closures besides cloning it before each closure?
  20. Why are recursive struct types illegal in Rust?
  21. Understanding Traits and Object Safety
  22. How do I pass a closure through raw pointers as an argument to a C function?
  23. Is there a way to use existing structs as enum variants?
  24. How can I create enums with constant values in Rust?
  25. Sized is not implemented for the type Fn
  26. Extend lifetime of variable
  27. Can’t implement a trait I don’t own for all types that implement a trait I do own
  28. Use of undeclared type or module `std` when used in a separate module
  29. Lazy sequence generation in Rust
  30. Is there a way to get the field names of a struct in a macro?

Leave a Comment