1. 31 5月, 2014 1 次提交
    • A
      std: Rename {Eq,Ord} to Partial{Eq,Ord} · 748bc3ca
      Alex Crichton 提交于
      This is part of the ongoing renaming of the equality traits. See #12517 for more
      details. All code using Eq/Ord will temporarily need to move to Partial{Eq,Ord}
      or the Total{Eq,Ord} traits. The Total traits will soon be renamed to {Eq,Ord}.
      
      cc #12517
      
      [breaking-change]
      748bc3ca
  2. 28 5月, 2014 4 次提交
  3. 25 5月, 2014 1 次提交
  4. 23 5月, 2014 2 次提交
  5. 17 5月, 2014 1 次提交
  6. 16 5月, 2014 1 次提交
    • A
      Updates with core::fmt changes · 1de4b65d
      Alex Crichton 提交于
      1. Wherever the `buf` field of a `Formatter` was used, the `Formatter` is used
         instead.
      2. The usage of `write_fmt` is minimized as much as possible, the `write!` macro
         is preferred wherever possible.
      3. Usage of `fmt::write` is minimized, favoring the `write!` macro instead.
      1de4b65d
  7. 14 5月, 2014 1 次提交
  8. 10 5月, 2014 1 次提交
    • A
      serialize: Ignore two flaky json tests on windows · 300109e5
      Alex Crichton 提交于
      See #14064 for some rationale, but the basic idea is that I suspect that there
      is an LLVM codegen bug somewhere, and I'm not entirely sure why it's happening
      intermittently rather than deterministically...
      
      cc #14064
      300109e5
  9. 09 5月, 2014 2 次提交
    • K
      Handle fallout in documentation · eab6bb2e
      Kevin Ballard 提交于
      Tweak the tutorial's section on vectors and strings, to slightly clarify
      the difference between fixed-size vectors, vectors, and slices.
      eab6bb2e
    • K
      Handle fallout in libserialize · cd3f31d9
      Kevin Ballard 提交于
      API Changes:
      
      - from_base64() returns Result<Vec<u8>, FromBase64Error>
      - from_hex() returns Result<Vec<u8>, FromHexError>
      - json::List is a Vec<Json>
      - Decodable is no longer implemented on ~[T] (but Encodable still is)
      - DecoderHelpers::read_to_vec() returns a Result<Vec<T>, E>
      cd3f31d9
  10. 07 5月, 2014 2 次提交
    • A
      core: Inherit non-allocating slice functionality · 91ede1f0
      Alex Crichton 提交于
      This commit adds a new trait, MutableVectorAllocating, which represents
      functions on vectors which can allocate.
      
      This is another extension trait to slices which should be removed once a lang
      item exists for the ~ allocation.
      91ede1f0
    • P
      librustc: Remove `~EXPR`, `~TYPE`, and `~PAT` from the language, except · 090040bf
      Patrick Walton 提交于
      for `~str`/`~[]`.
      
      Note that `~self` still remains, since I forgot to add support for
      `Box<self>` before the snapshot.
      
      How to update your code:
      
      * Instead of `~EXPR`, you should write `box EXPR`.
      
      * Instead of `~TYPE`, you should write `Box<Type>`.
      
      * Instead of `~PATTERN`, you should write `box PATTERN`.
      
      [breaking-change]
      090040bf
  11. 03 5月, 2014 1 次提交
  12. 02 5月, 2014 3 次提交
  13. 01 5月, 2014 2 次提交
  14. 29 4月, 2014 1 次提交
    • J
      Deprecate the rev_iter pattern in all places where a DoubleEndedIterator is... · 03609e5a
      Jonathan S 提交于
      Deprecate the rev_iter pattern in all places where a DoubleEndedIterator is provided (everywhere but treemap)
      
      This commit deprecates rev_iter, mut_rev_iter, move_rev_iter everywhere (except treemap) and also
      deprecates related functions like rsplit, rev_components, and rev_str_components. In every case,
      these functions can be replaced with the non-reversed form followed by a call to .rev(). To make this
      more concrete, a translation table for all functional changes necessary follows:
      
      * container.rev_iter() -> container.iter().rev()
      * container.mut_rev_iter() -> container.mut_iter().rev()
      * container.move_rev_iter() -> container.move_iter().rev()
      * sliceorstr.rsplit(sep) -> sliceorstr.split(sep).rev()
      * path.rev_components() -> path.components().rev()
      * path.rev_str_components() -> path.str_components().rev()
      
      In terms of the type system, this change also deprecates any specialized reversed iterator types (except
      in treemap), opting instead to use Rev directly if any type annotations are needed. However, since
      methods directly returning reversed iterators are now discouraged, the need for such annotations should
      be small. However, in those cases, the general pattern for conversion is to take whatever follows Rev in
      the original reversed name and surround it with Rev<>:
      
      * RevComponents<'a> -> Rev<Components<'a>>
      * RevStrComponents<'a> -> Rev<StrComponents<'a>>
      * RevItems<'a, T> -> Rev<Items<'a, T>>
      * etc.
      
      The reasoning behind this change is that it makes the standard API much simpler without reducing readability,
      performance, or power. The presence of functions such as rev_iter adds more boilerplate code to libraries
      (all of which simply call .iter().rev()), clutters up the documentation, and only helps code by saving two
      characters. Additionally, the numerous type synonyms that were used to make the type signatures look nice
      like RevItems add even more boilerplate and clutter up the docs even more. With this change, all that cruft
      goes away.
      
      [breaking-change]
      03609e5a
  15. 28 4月, 2014 2 次提交
  16. 19 4月, 2014 2 次提交
  17. 12 4月, 2014 1 次提交
  18. 10 4月, 2014 1 次提交
  19. 07 4月, 2014 2 次提交
  20. 01 4月, 2014 2 次提交
  21. 30 3月, 2014 1 次提交
  22. 29 3月, 2014 1 次提交
  23. 28 3月, 2014 2 次提交
  24. 19 3月, 2014 2 次提交
  25. 13 3月, 2014 1 次提交