- 25 3月, 2014 10 次提交
-
-
由 Brian Anderson 提交于
Also, add more distcheck tests
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
For integrating doc upload into the dist-snap process
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
Just to be more logical, put big headers between different installers
-
由 Brian Anderson 提交于
This doesn't work quite right yet (we need to build packages for all hosts) and I'm not ready to turn on new dist artifacts yet, but I want to start doing dry runs for 0.10, so I'm turning this off for now.
-
由 bors 提交于
While double-checking my understanding of the meaning of `'static`, I made the following test program: ```rust fn foo<X:'static>(_x: X) { } #[cfg(not(acceptable))] fn bar() { let a = 3; let b = &a; foo(b); } #[cfg(acceptable)] fn bar() { static c : int = 4;; let d : &'static int = &c; foo(d); } fn main() { bar(); } ``` Transcript of compiling above program, illustrating that the `--cfg acceptable` variant of `bar` compiles successfully, showing that the`'static` kind bound only disallows non-`static` references, not *all* references: ``` % rustc --version /Users/fklock/opt/rust-dbg/bin/rustc 0.10-pre (caf17fea 2014-03-21 02:21:50 -0700) host: x86_64-apple-darwin % rustc /tmp/s.rs /tmp/s.rs:7:5: 7:8 error: instantiating a type parameter with an incompatible type `&int`, which does not fulfill `'static` /tmp/s.rs:7 foo(b); ^~~ error: aborting due to previous error % rustc --cfg acceptable /tmp/s.rs % ./s % ``` (Note that the explicit type annotation on `let d : &'static int` is necessary; it did not suffice for me to just write `let d = &'static c;`. That might be a latent bug, I am not sure yet.) Anyway, a fix to the documentation seemed prudent.
-
- 24 3月, 2014 10 次提交
-
-
由 bors 提交于
syntax: allow `trace_macros!` and `log_syntax!` in item position. Previously trace_macros!(true) fn main() {} would complain about `trace_macros` being an expression macro in item position. This is a pointless limitation, because the macro is purely compile-time, with no runtime effect. (And similarly for log_syntax.) This also changes the behaviour of `trace_macros!` very slightly, it used to be equivalent to macro_rules! trace_macros { (true $($_x: tt)*) => { true }; (false $($_x: tt)*) => { false } } I.e. you could invoke it with arbitrary trailing arguments, which were ignored. It is changed to accept only exactly `true` or `false` (with no trailing arguments) and expands to `()`.
-
由 Felix S. Klock II 提交于
While double-checking my understanding of the meaning of `'static`, I made the following test program: ```rust fn foo<X:'static>(_x: X) { } #[cfg(not(acceptable))] fn bar() { let a = 3; let b = &a; foo(b); } #[cfg(acceptable)] fn bar() { static c : int = 4;; let d : &'static int = &c; foo(d); } fn main() { bar(); } ``` Transcript of compiling above program, illustrating that the `--cfg acceptable` variant of `bar` compiles successfully, showing that the `'static` kind bound only disallows non-`static` references, not *all* references: ``` % rustc --version /Users/fklock/opt/rust-dbg/bin/rustc 0.10-pre (caf17fea 2014-03-21 02:21:50 -0700) host: x86_64-apple-darwin % rustc /tmp/s.rs /tmp/s.rs:7:5: 7:8 error: instantiating a type parameter with an incompatible type `&int`, which does not fulfill `'static` /tmp/s.rs:7 foo(b); ^~~ error: aborting due to previous error % rustc --cfg acceptable /tmp/s.rs % ./s % ``` (Note that the explicit type annotation on `let d : &'static int` is necessary; it did not suffice for me to just write `let d = &'static c;`. That might be a latent bug, I am not sure yet.) Anyway, a fix to the documentation seemed prudent.
-
由 bors 提交于
Rust doc sprint: adding doc strings to the Terminfo library. This is my very first Rust repository PR, so please do not hold back any formatting, nit-picky commentary. I need it.
-
由 Olle Jonsson 提交于
-
由 bors 提交于
-
由 bors 提交于
This commit moves from {read,emit}_seq for tuples to {read,emit}_tuple, as well as providing a generalized macro for generating these implementations from one invocation. Closes #13086
-
由 Steven Stewart-Gallus 提交于
-
由 bors 提交于
Fixes #12992 I tried to increase the number of deflate's probes. Reduction of 0.5% or 2% is not enough.
-
由 bors 提交于
-
由 Alex Crichton 提交于
This commit moves from {read,emit}_seq for tuples to {read,emit}_tuple, as well as providing a generalized macro for generating these implementations from one invocation. Closes #13086
-
- 23 3月, 2014 20 次提交
-
-
由 bors 提交于
std: remove the `equals` method from `TotalEq`. `TotalEq` is now just an assertion about the `Eq` impl of a type (i.e. `==` is a total equality if a type implements `TotalEq`) so the extra method is just confusing. Also, a new method magically appeared as a hack to allow deriving to assert that the contents of a struct/enum are also TotalEq, because the deriving infrastructure makes it very hard to do anything but create a trait method. (You didn't hear about this horrible work-around from me :(.)
-
由 Ms2ger 提交于
-
由 bors 提交于
-
由 bors 提交于
This will make the types more readable in the documentation, since the letters correspond with what you should either be sending or expecting to receive.
-
由 Huon Wilson 提交于
`TotalEq` is now just an assertion about the `Eq` impl of a type (i.e. `==` is a total equality if a type implements `TotalEq`) so the extra method is just confusing. Also, a new method magically appeared as a hack to allow deriving to assert that the contents of a struct/enum are also TotalEq, because the deriving infrastructure makes it very hard to do anything but create a trait method. (You didn't hear about this horrible work-around from me :(.)
-
由 Piotr Czarnecki 提交于
Fixes #12992 Store compressed bitcode files in rlibs with a different extension. Compression doesn't interfere with --emit=bc. Regression test compares outputs.
-
由 bors 提交于
`Vec` is now used for the internal buffer instead of `~[]`. Some module level documentation somehow ended up attached to `BufferedReader` so I fixed that as well.
-
由 Flavio Percoco 提交于
-
由 bors 提交于
This has been rendered obsolete by partial type hints. Since the `~[T]` type is in the process of being removed, it needs to go away.
-
由 Daniel Micay 提交于
This needs to be removed as part of removing `~[T]`. Partial type hints are now allowed, and will remove the need to add a version of this method for `Vec<T>`. For now, this involves a few workarounds for partial type hints not completely working.
-
由 bors 提交于
Closes #5283
-
由 Daniel Micay 提交于
Closes #5283
-
由 bors 提交于
This removes two tests built on `managed::refcount`, but these issues are well-covered elsewhere for non-managed types.
-
由 Daniel Micay 提交于
This removes two tests built on `managed::refcount`, but these issues are well-covered elsewhere for non-managed types.
-
由 Ryan Scheel (Havvy) 提交于
-
由 Steven Fackler 提交于
`Vec` is now used for the internal buffer instead of `~[]`. Some module level documentation somehow ended up attached to `BufferedReader` so I fixed that as well.
-
由 bors 提交于
Implements vtable support for generic Deref impls with trait bounds. Also fixes cross-crate inlining when using autoderef.
-
由 Eduard Burtescu 提交于
Closes #13044.
-
由 bors 提交于
-
由 Eduard Burtescu 提交于
Closes #13042.
-