1. 14 8月, 2014 1 次提交
    • B
      std: Rename various slice traits for consistency · 4f5b6927
      Brian Anderson 提交于
      ImmutableVector -> ImmutableSlice
      ImmutableEqVector -> ImmutableEqSlice
      ImmutableOrdVector -> ImmutableOrdSlice
      MutableVector -> MutableSlice
      MutableVectorAllocating -> MutableSliceAllocating
      MutableCloneableVector -> MutableCloneableSlice
      MutableOrdVector -> MutableOrdSlice
      
      These are all in the prelude so most code will not break.
      
      [breaking-change]
      4f5b6927
  2. 13 8月, 2014 1 次提交
  3. 12 8月, 2014 4 次提交
  4. 11 8月, 2014 1 次提交
    • J
      API docs/examples for std::slice · 371e8cf2
      Jason Thompson 提交于
       - API doc/example for next() in Permutations
       - API doc/example for permutations() in ImmutableCloneableVector
       - Moved examples for permutations and next into trait definition as
         comments on pull request #16244.
       - Fix erroneus inclusion of src/llvm in older commit.
      371e8cf2
  5. 08 8月, 2014 1 次提交
    • N
      Cleanup collections::slice documentation. · cb0aa8ac
      nham 提交于
      This does a few things:
      
       - remove references to ~[] and the OwnedVector trait, which are both
         obsolete
       - correct the docs to say that this is the slice module, not the vec
         module
       - add a sentence pointing out that vectors are distinct from Vec
       - remove documentation on Vec.
      
      closes #15459
      cb0aa8ac
  6. 07 8月, 2014 2 次提交
  7. 06 8月, 2014 1 次提交
  8. 03 8月, 2014 1 次提交
  9. 02 8月, 2014 4 次提交
  10. 01 8月, 2014 1 次提交
    • P
      librustc: Forbid pattern bindings after `@`s, for memory safety. · 5b85c8cb
      Patrick Walton 提交于
      This is an alternative to upgrading the way rvalues are handled in the
      borrow check. Making rvalues handled more like lvalues in the borrow
      check caused numerous problems related to double mutable borrows and
      rvalue scopes. Rather than come up with more borrow check rules to try
      to solve these problems, I decided to just forbid pattern bindings after
      `@`. This affected fewer than 10 lines of code in the compiler and
      libraries.
      
      This breaks code like:
      
          match x {
              y @ z => { ... }
          }
      
          match a {
              b @ Some(c) => { ... }
          }
      
      Change this code to use nested `match` or `let` expressions. For
      example:
      
          match x {
              y => {
                  let z = y;
                  ...
              }
          }
      
          match a {
              Some(c) => {
                  let b = Some(c);
                  ...
              }
          }
      
      Closes #14587.
      
      [breaking-change]
      5b85c8cb
  11. 31 7月, 2014 1 次提交
  12. 30 7月, 2014 3 次提交
  13. 29 7月, 2014 1 次提交
  14. 28 7月, 2014 9 次提交
  15. 27 7月, 2014 7 次提交
  16. 26 7月, 2014 2 次提交