| Age | Commit message (Collapse) | Author | Lines |
|---|
|
There are multiple issues with them as designed and implemented.
cc #27364
Conflicts:
src/libsyntax/feature_gate.rs
src/test/auxiliary/xcrate_associated_type_defaults.rs
|
|
This recently regressed in #24689, and this updates the `Display` implementation
to take formatting flags into account.
Closes #26625
|
|
These will first be deprecated in 1.2.0, not 1.1.0.
|
|
This removes a footgun, since it is a reasonable assumption to make that
pointers to `T` will be aligned to `align_of::<T>()`. This also matches
the behaviour of C/C++. `min_align_of` is now deprecated.
Closes #21611.
|
|
`core::num::from_str_radix` can't parse the prefix `+` .
http://is.gd/ewo0T2
|
|
`core::num::from_str_radix` can't parse the prefix `+` .
http://is.gd/ewo0T2
|
|
|
|
* Add `#[doc(hidden)]`
* Rename away from `Error::description`
|
|
Also add `#[doc(hidden)]` to a few internal functions.
|
|
|
|
This commit stabilizes the `str::{matches, rmatches}` functions and iterators,
but renames the unstable feature for the `str::{matches,rmatches}_indices`
function to `str_match_indices` due to the comment present on the functions
about the iterator's return value.
|
|
This commit stabilizes these two iterator primitives as they have gone through
the RFC process and had some time to bake now.
|
|
This commit stabilizes the remaining `wrapping_*` functions on the primitive
integer types as they follow the same conventions as other wrapping methods are
were likely just initially unstable to be conservative.
|
|
These constants have been unstable for some time now already
|
|
These were just exposed to be used elsewhere at some point, but neither is
currently being used so just make them private again.
|
|
This trait has seen very little usage and while safe, may not belong in the
standard library.
|
|
This function has seen very little use and it seems better to explore this
functionality through iterator adaptors instead of specialized functions.
|
|
Unsafe patterns such as `slice::from_raw_parts` and `CStr::from_ptr` have shown
that dealing with lifetimes, while useful, is often a hindrance. Consequently
these functions are rarely called today and are being deprecated.
|
|
Neither of these iterators has seen enough usage to justify their position in
the standard library, so these unstable iterators are being slated for deletion.
|
|
This trait has not proven itself over time as being core and fundamentally
useful to iterators, so it's being deprecated to allow time to iterate on it out
of tree.
|
|
|
|
This commit shards the broad `core` feature of the libcore library into finer
grained features. This split groups together similar APIs and enables tracking
each API separately, giving a better sense of where each feature is within the
stabilization process.
A few minor APIs were deprecated along the way:
* Iterator::reverse_in_place
* marker::NoCopy
|
|
Also, it feels more suitable to use hex to represent unicode
|
|
Because these structures are created by a macro, the doc comments
don't quite work: the leading /// isn't stripped. Instead, just
use #[doc] so that they render correctly.
|
|
Because these structures are created by a macro, the doc comments
don't quite work: the leading /// isn't stripped. Instead, just
use #[doc] so that they render correctly.
|
|
As it says in the title. I've added an `expect` method to `Result` that allows printing both an error message (e.g. what operation was attempted), and the error value. This is separate from the `unwrap` and `ok().expect("message")` behaviours.
|
|
|
|
`FormatError` is not exist anymore.
|
|
|
|
Pull request for #26188.
|
|
- Successful merges: #26181, #26184, #26189, #26191, #26195, #26202
- Failed merges:
|
|
Closes #26169.
r? @steveklabnik
|
|
core: impl Clone for option::IntoIter and iter::Once
|
|
Various methods in both libcore/char.rs and librustc_unicode/char.rs were previously marked with #[inline], now every method is marked in char's impl blocks.
Partially fixes #26124.
EDIT: I'm not familiar with pull reqests (yet), apparently Github added my second commit to thit PR...
Fixes #26124
|
|
Implement RFC rust-lang/rfcs#1123
Add str method str::split_at(mid: usize) -> (&str, &str).
Also a minor cleanup in the collections::str module. Remove redundant slicing of self.
|
|
This is the logical next step after #24661, but I’m less sure about this one.
r? @alexcrichton
|
|
|
|
|
|
|
|
This is the logical next step after #24661, but I’m less sure about this one.
|
|
Swap arguments of `assert_eq!` calls, insert additional assertions
here and there.
Closes #26169.
|
|
Implement RFC rust-lang/rfcs#1123
Add str method str::split_at(mid: usize) -> (&str, &str).
|
|
|
|
Using two terms for one thing is confusing, these are called 'raw pointers' today.
|
|
r? @eddyb
|
|
|
|
When things get stabilized, they don't always have their docs updated to remove the gate.
|
|
When things get stabilized, they don't always have their docs updated to remove the gate.
|
|
|
|
The API documentation is not explicit enough that because `try!` returns
`Err` early for you, you can only use it in functions that return
`Result`. The book mentions this, but if you come across `try!` outside
of the book and look it up in the docs, this restriction on the return
type of the function is not particularly clear.
|
