- 15 2月, 2015 16 次提交
-
-
由 Manish Goregaokar 提交于
While having a look at the Rust book I found this tiny error. In my opinion this if should be all lowercase, because it follows a colon, but I am no native speaker, so I am probably wrong. Also it is a very tiny change, so feel free to include it in any bigger documentation patch.
-
由 Manish Goregaokar 提交于
Removes the link to the rust-dev mailing list in the bug report submission page and also adds the address of the IRC server (`irc.mozilla.org`). Addresses #22249.
-
由 Manish Goregaokar 提交于
`Unsafe` was renamed to `UnsafeCell` a while ago, but the corresponding lang item kept the old name. This patch fixes the inconsistency. r? @EddyB
-
由 Manish Goregaokar 提交于
In `std::f32` and `std::f64`: - `MIN_VALUE` → `MIN` - `MAX_VALUE` → `MAX` - `MIN_POS_VALUE` → `MIN_POSITIVE` This matches the corresponding integer constants. [breaking-change]
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
Fixes #22233 r? @alexcrichton
-
由 Manish Goregaokar 提交于
According to @dotdash it enables more aggressive optimizations from LLVM
-
由 Manish Goregaokar 提交于
Fix #20109.
-
由 Manish Goregaokar 提交于
This overhauls the very meager docs that currently exist to clarify various understandable confusions that I've noticed, e.g. people look in `std::raw` for the "real" types of slices like `&[T]`, or think that `Slice<T>` refers to `[T]` (fixes #22214). This patch takes the liberty of offering some "style" guidance around `raw::Slice`, since there's more restricted ways to duplicate all functionality connected to it: `std::slice::from_raw_parts{,_mut}` for construction and `.as_{,mut_}ptr` & `.len` for deconstruction. It also deprecates the `std::raw::Closure` type which is now useless for non-type-erased closures, and replaced by `TraitObject` for `&Fn`, `&mut FnMut` etc, so I guess it should be called a: [breaking-change]
-
由 Manish Goregaokar 提交于
rustc --version says ``` rustc 1.0.0-dev (d0e82a68 2015-02-05 14:38:56 -0800) (built 2015-02-11) ```
-
由 Manish Goregaokar 提交于
Fixes #16645 Fixing this in any deeper way will require an RFC, so let's just document the current behavior.
-
由 bors 提交于
This is super black magic internals at the moment, but having it somewhere semi-public seems good. The current versions weren't being rendered, and they'll be useful for some people. Fixes #21281 r? @nikomatsakis @kmcallister
-
由 bors 提交于
Working on just knocking these out for all the collections so that there's something there.
-
由 Alexis 提交于
-
由 Steve Klabnik 提交于
-
由 bors 提交于
It is only allowed in paths now, where it will either work inside a `trait` or `impl` item, or not resolve outside of it. [breaking-change] Closes #22137
-
- 14 2月, 2015 11 次提交
-
-
由 bors 提交于
This ended up just being a forgotten attribute on the `char` module in libunicode. Closes #22084
-
由 bors 提交于
Per [RFC 579](https://github.com/rust-lang/rfcs/pull/579), this commit adds a new `std::process` module. This module is largely based on the existing `std::old_io::process` module, but refactors the API to use `OsStr` and other new standards set out by IO reform. The existing module is not yet deprecated, to allow for the new API to get a bit of testing before a mass migration to it.
-
由 Aaron Turon 提交于
Per [RFC 579](https://github.com/rust-lang/rfcs/pull/579), this commit adds a new `std::process` module. This module is largely based on the existing `std::old_io::process` module, but refactors the API to use `OsStr` and other new standards set out by IO reform. The existing module is not yet deprecated, to allow for the new API to get a bit of testing before a mass migration to it.
-
由 bors 提交于
the sed option `--in-place` (or `-i`) is a GNU extension, and it is not portable to BSD system (openbsd and freebsd checked). use an alternate construction in order to keep the semantic.
-
由 bors 提交于
Replaced outdated use of the `range(start, end)` function where appropriate with `start..end`, and tweaked the examples to compile and run with the latest rust. I also fixed two periphery compile issues in reference.md which were occluding whether there were any new errors created by these changes.
-
由 Ulrik Sverdrup 提交于
The default implementation of .repr() will call conveniently call transmute_copy which should be appropriate for all implementors, but is memory unsafe if used wrong. Fixes #22260 You need to use `unsafe impl` to implement the Repr trait now. [breaking-change]
-
由 Huon Wilson 提交于
This overhauls the very meager docs that currently exist to clarify various understandable confusions that I've noticed, e.g. people look in `std::raw` for the "real" types of slices like `&[T]`, or think that `Slice<T>` refers to `[T]` (fixes #22214). This patch takes the liberty of offering some "style" guidance around `raw::Slice`, since there's more restricted ways to duplicate all functionality connected to it: `std::slice::from_raw_parts{,_mut}` for construction and `.as_{,mut_}ptr` & `.len` for deconstruction. It also deprecates the `std::raw::Closure` type which is now useless for non-type-erased closures, and replaced by `TraitObject` for `&Fn`, `&mut FnMut` etc, so I guess it should be called a: [breaking-change]
-
由 bors 提交于
This PR adds a dedicated regression test for #15881 as @cmr suggested.
-
由 Brian Anderson 提交于
rustc --version says ``` rustc 1.0.0-dev (d0e82a68 2015-02-05) (built 2015-02-11) ```
-
由 bors 提交于
This PR is an optimization of the `FromIterator` implementation of `Vec` Benchmark: https://gist.github.com/alexcrichton/03d666159a28a80e7c70 Before: test macro_repeat1 ... bench: 57 ns/iter (+/- 1) test macro_repeat2 ... bench: 56 ns/iter (+/- 1) test map_clone1 ... bench: 828 ns/iter (+/- 13) test map_clone2 ... bench: 828 ns/iter (+/- 8) test repeat1 ... bench: 1104 ns/iter (+/- 10) test repeat2 ... bench: 1106 ns/iter (+/- 11) After: test macro_repeat1 ... bench: 75 ns/iter (+/- 21) test macro_repeat2 ... bench: 59 ns/iter (+/- 31) test map_clone1 ... bench: 34 ns/iter (+/- 22) test map_clone2 ... bench: 52 ns/iter (+/- 21) test repeat1 ... bench: 34 ns/iter (+/- 11) test repeat2 ... bench: 33 ns/iter (+/- 12) The idea behind this optimization is to avoid all bounds checks for space already allocated into the vector. This may involve running the iterator twice, but the first run of the iterator should be optimizable to a memcpy or memset if possible. The same treatment can in theory be applied to `Vec::extend` but the benchmarks for that currently get *worse* if the change is applied. This appears to be some LLVM optimizations going awry but it's seems prudent to land at least the `collect` portion beforehand.
-
由 Steve Klabnik 提交于
-
- 13 2月, 2015 13 次提交
-
-
由 Steve Klabnik 提交于
Fixes #16645
-
由 Florian Hahn 提交于
-
由 Kevin Yap 提交于
Also add address of IRC server. Addresses #22249.
-
由 bors 提交于
Names of structs, enums, traits, type aliases and type parameters (i.e. all identifiers that can be used as full paths in type position) are not allowed to match the names of primitive types. See #20427 for more information. This is a minor [breaking-change]
-
由 Chris Wong 提交于
-
由 Chris Wong 提交于
-
由 Huon Wilson 提交于
In `std::f32` and `std::f64`: - `MIN_VALUE` → `MIN` - `MAX_VALUE` → `MAX` - `MIN_POS_VALUE` → `MIN_POSITIVE` This matches the corresponding integer constants. [breaking-change]
-
由 bors 提交于
borrowck: Prevent partial reinitialization of uninitialized structures This is a pnkfelix-swiped squash of #22079, which was a rebase and revision of #18963 Fixes #18571.
-
由 Duane Edwards 提交于
-
由 Marvin Löbel 提交于
It is only allowed in paths now, where it will either work inside a `trait` or `impl` item, or not resolve outside of it. [breaking-change] Closes #22137
-
由 Björn Steinbrink 提交于
Fixes #22233
-
由 bors 提交于
This resolves a number of bugs that trigger stack overflows or other cyclic errors. r? @nick29581 (it is based on work that you started) f? @jroesch (also based on your branch)
-
由 Niko Matsakis 提交于
-