| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Specifically:
* Peekable
* ByRef
* Skip
* Take
* Fuse
Fixes #20547
|
|
|
|
This PR is intended as alternative to #20958. It fixes the same grammar inconsistencies, but does not increase the operator precedence of `..`, leaving it at the same level as the assignment operator.
For previous discussion, see #20811 and #20958.
Grammar changes:
* allow `for _ in 1..i {}` (fixes #20241)
* allow `for _ in 1.. {}` as infinite loop
* prevent use of range notation in contexts where only operators of high precedence are expected (fixes #20811)
Parser code cleanup:
* remove `RESTRICTION_NO_DOTS`
* make `AS_PREC` const and follow naming convention
* make `min_prec` inclusive
r? nikomatsakis
|
|
This pull request add tooltips to most links of sidebar.
The tooltips display "summary line" of items' document.
Some lengthy/annoying raw markdown code are eliminated, such as links and headers.
- `[Rust](http://rust-lang.org)` displays as `Rust` (no URLs)
- `# header` displays as `header` (no `#`s)
Some inline spans, e.g. ``` `code` ``` and ```*emphasis*```, are kept as they are, for better readable.
I've make sure `&` `'` `"` `<` and `>` are properly displayed in tooltips, for example, `&'a Option<T>`.
Online preview: http://liigo.com/tmp/tooltips/std/index.html
@alexcrichton @steveklabnik since you have reviewed my previous ([v1](https://github.com/rust-lang/rust/pull/13014),[v2](https://github.com/rust-lang/rust/pull/16448)) PRs of this serise, which have been closed for technical reasons. Thank you.
|
|
There are doc improvements as well as these conversions:
- int/uint -> isize/usize
- u/i -> us/is
|
|
Lifetime elision documentation was reference a previously existing function
that doesn't exist. After talking with Steve Klabnik, I confirmed the correct
function to be referenced and updated documentation accordingly.
|
|
|
|
When I wrote this code, my janky shim to verify the constants didn't
work as intended.
This fixes everything I've run into since merge, which is hopefully
everything.
|
|
Make compiletest set an environment variable so that on Windows 32-bit test executables containing certain substrings (e.g. 'install', 'setup', 'update', 'patch') are not blocked by UAC's Installer Detection Technology.
|
|
|
|
Fixes #21430
|
|
Fixes #21440"
|
|
Fixes #21469.
|
|
This should fix issue #20797 (but I don't want to close it automatically).
As the actual fix is very small this would be a perfect candidate for a rollup.
|
|
Compiling won't produce an executable just yet because (as stated in the next
paragraph) there are errors. By removing this sentance, the reader won't get
confused when they expect a successful compile i.e. if they don't read ahead one
paragraph, they are going to be checking their code and wondering why it's not
compiling.
|
|
Updated incorrect error messages, and removed explicit return statements from example code.
|
|
Previous wording wasn’t clear about its actual behaviour. It could be
interpreted as answering either:
* Can current thread panic?
* Is current thread unwinding because of panic?
r? @steveklabnik
|
|
Not sure on what *exactly* should be said here, but I think this is the most important bit. This PR also establishes conventions for describing performance minimally.
I suggest to describe preformance for individual methods we use a `# Performance` heading. Not sure if we should have
```
# Performance: O(1)
details details
```
or
```
# Performance:
O(1)
details details
```
Since I think most methods don't need discussion, the former seems more resonable. But it's kind of weird to have info "in" the heading.
r? @steveklabnik
|
|
Fixes #6444
I need some help with the macro docs here, as I couldn't figure it out. @kmcallister @eddyb or someone else?
|
|
When we moved over to the book, we lost this.
|
|
Fixes #6444
|
|
|
|
Grammar changes:
* allow 'for _ in 1..i {}' (fixes #20241)
* allow 'for _ in 1.. {}' as infinite loop
* prevent use of range notation in contexts where only operators of high
precedence are expected (fixes #20811)
Parser code cleanup:
* remove RESTRICTION_NO_DOTS
* make AS_PREC const and follow naming convention
* make min_prec inclusive
|
|
When we moved over to the book, we lost this.
|
|
|
|
* Include an illustration of a function that accepts two closures.
|
|
rebase and fix of #19267
|
|
When I wrote this code, my janky shim to verify the constants didn't
work as intended.
This fixes everything I've run into since merge, which is hopefully
everything.
|
|
|
|
executables containing certain substrings (e.g. 'install', 'setup', 'update', 'patch') are not blocked by UAC's Installer Detection Technology.
|
|
ByRef is not tested included because it is a trivial pass through.
|
|
|
|
This reverts commit a729a404945de10f99e2530a5c28952996532b29.
|
|
This reverts commit 9bbfd681c9fa47f462a89e8f5eedd3fa2a5de2e7.
|
|
This reverts commit a7525bc4c8eb8507a5c248d29286e77133217cf3.
|
|
|
|
Fixes #21430
|
|
Conflicts:
src/librustc/diagnostics.rs
src/librustdoc/clean/mod.rs
src/librustdoc/html/format.rs
src/libsyntax/parse/parser.rs
|
|
Fixes #21440"
|
|
Conflicts:
src/libcore/ops.rs
src/librustc_typeck/astconv.rs
src/libstd/io/mem.rs
src/libsyntax/parse/lexer/mod.rs
|
|
Project region bounds out of the trait when deciding whether a projection type outlives a given regions.
Fixes #20890.
Fixes #21150.
|
|
Conflicts:
src/librustc_trans/trans/debuginfo.rs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #21469.
|
