1. 03 1月, 2014 1 次提交
  2. 30 12月, 2013 1 次提交
  3. 29 12月, 2013 1 次提交
  4. 12 12月, 2013 1 次提交
  5. 10 12月, 2013 1 次提交
  6. 08 12月, 2013 1 次提交
  7. 29 11月, 2013 1 次提交
  8. 22 10月, 2013 1 次提交
  9. 08 10月, 2013 2 次提交
    • B
      add new enum ast::StrStyle as field to ast::lit_str · 9d7b1300
      Benjamin Herr 提交于
      For the benefit of the pretty printer we want to keep track of how
      string literals in the ast were originally represented in the source
      code.
      
      This commit changes parser functions so they don't extract strings from
      the token stream without at least also returning what style of string
      literal it was. This is stored in the resulting ast node for string
      literals, obviously, for the package id in `extern mod = r"package id"`
      view items, for the inline asm in `asm!()` invocations.
      
      For `asm!()`'s other arguments or for `extern "Rust" fn()` items, I just
      the style of string, because it seemed disproportionally cumbersome to
      thread that information through the string processing that happens with
      those string literals, given the limited advantage raw string literals
      would provide in these positions.
      
      The other syntax extensions don't seem to store passed string literals
      in the ast, so they also discard the style of strings they parse.
      9d7b1300
    • B
      add token::LIT_STR_RAW(ident, num of # symbols) · 97878725
      Benjamin Herr 提交于
      Treat it as a synonym for LIT_STR for now.
      97878725
  10. 02 10月, 2013 1 次提交
    • D
      remove the `float` type · c9d4ad07
      Daniel Micay 提交于
      It is simply defined as `f64` across every platform right now.
      
      A use case hasn't been presented for a `float` type defined as the
      highest precision floating point type implemented in hardware on the
      platform. Performance-wise, using the smallest precision correct for the
      use case greatly saves on cache space and allows for fitting more
      numbers into SSE/AVX registers.
      
      If there was a use case, this could be implemented as simply a type
      alias or a struct thanks to `#[cfg(...)]`.
      
      Closes #6592
      
      The mailing list thread, for reference:
      
      https://mail.mozilla.org/pipermail/rust-dev/2013-July/004632.html
      c9d4ad07
  11. 01 10月, 2013 1 次提交
  12. 07 9月, 2013 2 次提交
    • J
      quote_* macros no longer need to be capturing · 1ecc1e51
      John Clements 提交于
      This is actually almost a problem, because those were my poster-child
      macros for "here's how to implement a capturing macro." Following this
      change, there will be no macros that use capturing; this will probably
      make life unpleasant for the first person that wants to implement a
      capturing macro. I should probably create a dummy_capturing macro,
      just to show how it works.
      1ecc1e51
    • J
      capturing macros now implemented · b9bb4abc
      John Clements 提交于
      b9bb4abc
  13. 04 9月, 2013 1 次提交
  14. 03 9月, 2013 1 次提交
  15. 02 9月, 2013 1 次提交
  16. 01 9月, 2013 1 次提交
  17. 19 8月, 2013 1 次提交
  18. 13 8月, 2013 1 次提交
  19. 04 8月, 2013 1 次提交
  20. 02 8月, 2013 2 次提交
    • O
      Replace 'blk' -> 'block' in AstBuilder. · 09efc4e8
      OGINO Masanori 提交于
      I didn't rename variables because they are local and are not parts of
      the public interfaces.
      Signed-off-by: NOGINO Masanori <masanori.ogino@gmail.com>
      09efc4e8
    • B
      Remove the pipes compiler · 4b3e766a
      Brian Anderson 提交于
      The pipes compiler produced data types that encoded efficient and safe
      bounded message passing protocols between two endpoints. It was also
      capable of producing unbounded protocols.
      
      It was useful research but was arguably done before its proper time.
      
      I am removing it for the following reasons:
      
      * In practice we used it only for producing the `oneshot` and `stream`
        unbounded protocols and all communication in Rust use those.
      * The interface between the proto! macro and the standard library
        has a large surface area and was difficult to maintain through
        language and library changes.
      * It is now written in an old dialect of Rust and generates code
        which would likely be considered non-idiomatic.
      * Both the compiler and the runtime are difficult to understand,
        and likewise the relationship between the generated code and
        the library is hard to understand. Debugging is difficult.
      * The new scheduler implements `stream` and `oneshot` by hand
        in a way that will be significantly easier to maintain.
      
      This shouldn't be taken as an indication that 'channel protocols'
      for Rust are not worth pursuing again in the future.
      4b3e766a
  21. 01 8月, 2013 1 次提交
  22. 22 7月, 2013 1 次提交
  23. 18 7月, 2013 2 次提交
  24. 13 7月, 2013 1 次提交
  25. 07 7月, 2013 1 次提交
  26. 26 6月, 2013 1 次提交
  27. 23 6月, 2013 1 次提交
    • D
      vec: remove BaseIter implementation · d2e9912a
      Daniel Micay 提交于
      I removed the `static-method-test.rs` test because it was heavily based
      on `BaseIter` and there are plenty of other more complex uses of static
      methods anyway.
      d2e9912a
  28. 16 6月, 2013 1 次提交
  29. 14 6月, 2013 1 次提交
  30. 13 6月, 2013 1 次提交
    • H
      Use @str instead of @~str in libsyntax and librustc. Fixes #5048. · 096f6f56
      Huon Wilson 提交于
      This almost removes the StringRef wrapper, since all strings are
      Equiv-alent now. Removes a lot of `/* bad */ copy *`'s, and converts
      several things to be &'static str (the lint table and the intrinsics
      table).
      
      There are many instances of .to_managed(), unfortunately.
      096f6f56
  31. 12 6月, 2013 2 次提交
  32. 10 6月, 2013 1 次提交
  33. 07 6月, 2013 1 次提交
  34. 06 6月, 2013 2 次提交