Can Rust optimise away the bit-wise copy during move of an object someday?

by

Given that in Rust (unlike C or C++) the address of a value is not considered to matter, there is nothing in terms of language that prevents the elision of the copy.

However, today rustc does not optimize anything: all optimizations are delegated to LLVM, and it seems you have hit a limitation of the LLVM optimizer here (it’s unclear whether this limitation is due to LLVM being close to C’s semantics or is just an omission).

So, there are two avenues of improving code generation for this:

  • teaching LLVM to perform this optimization (if possible)
  • teaching rustc to perform this optimization (optimization passes are coming to rustc now that it has MIR)

but for now you might simply want to avoid such large objects from being allocated on the stack, you can Box it for example.

More Related Contents:

  1. What are move semantics in Rust?
  2. How does Rust provide move semantics?
  3. Why is the mutable reference not moved here?
  4. Why does the compiler not complain that an iterator moved to a for loop is immutable?
  5. Why can’t I store a value and a reference to that value in the same struct?
  6. How do I stop iteration and return an error when Iterator::map returns a Result::Err?
  7. Why does Iterator::take_while take ownership of the iterator?
  8. When should I implement std::convert::From vs std::convert::Into?
  9. Efficiently mutate a vector while also iterating over the same vector
  10. How can I call a mutating method while holding a reference to self?
  11. How do I use the Entry API with an expensive key that is only constructed if the Entry is Vacant?
  12. “parameter `’a` is never used” error when ‘a is used in type parameter bound
  13. Borrowing references to attributes in a struct
  14. How do I split a string in Rust?
  15. Is it possible to implement methods on type aliases?
  16. How can I modify self in a closure called from a member function?
  17. How do I synchronously return a value calculated in an asynchronous Future?
  18. How do I move out of a struct field that is an Option?
  19. Removing elements from a Vec based on some condition [duplicate]
  20. How can I change enum variant while moving the field to the new variant?
  21. What is unwrap in Rust, and what is it used for?
  22. The trait `FnMut` is not implemented for `String` when trying to split a string
  23. HashMap borrow issue when trying to implement find or insert
  24. How can I find a subsequence in a &[u8] slice?
  25. Why “explicit lifetime bound required” for Box in struct?
  26. How to print a Vec?
  27. How to get an Option’s value or set it if it’s empty?
  28. Rust equivalent to Swift’s extension methods to a protocol?
  29. How can I solve “use of moved value” and “which does not implement the `Copy` trait”?
  30. Why does using Option::map to Box::new a trait object not work?

Leave a Comment