1. 13 1月, 2016 1 次提交
  2. 09 1月, 2016 3 次提交
  3. 08 1月, 2016 3 次提交
    • S
      Change destination accessor to return references · 2f86c160
      Simonas Kazlauskas 提交于
      Previously it was returning a value, mostly for the two reasons:
      
      * Cloning Lvalue is very cheap most of the time (i.e. when Lvalue is not a Projection);
      * There’s users who want &mut lvalue and there’s users who want &lvalue. Returning a value allows
        to make either one easier when pattern matching (i.e. Some(ref dest) or Some(ref mut dest)).
      
      However, I’m now convinced this is an invalid approach. Namely the users which want a mutable
      reference may modify the Lvalue in-place, but the changes won’t be reflected in the final MIR,
      since the Lvalue modified is merely a clone.
      
      Instead, we have two accessors `destination` and `destination_mut` which return a reference to the
      destination in desired mode.
      2f86c160
    • F
      40e2ac28
    • S
      Expand EO308 to mention try! · ce49e322
      Steve Klabnik 提交于
      Fixes #28953
      ce49e322
  4. 07 1月, 2016 5 次提交
  5. 06 1月, 2016 19 次提交
  6. 05 1月, 2016 6 次提交
  7. 03 1月, 2016 3 次提交