| Age | Commit message (Collapse) | Author | Lines |
|
|
|
Fixes #24774.
r? @steveklabnik
|
|
Update 7.2.20 (`for` expressions):
* `for` loops now use `IntoIterator` instead of just `Iterator`
* Simplify the example by removing unnecessary `Vec::iter` call.
...and a fix for a minor formatting error.
r? @steveklabnik
|
|
FIxes #24712
|
|
Changed in #22838.
audited (raw) byte string literals @ #16676
|
|
As part of the audit for #22820 the following duplicate feature
gate tests were removed:
* `box_patterns`
* `simd_ffi`
These tests for `box_patterns` and `simd_ffi` were added in #23578,
however there were existing tests in #20723 and #21233 respectively.
r? @nrc
|
|
As part of the audit for #22820 the following feature gate tests have been
added:
* `negate_unsigned`
* `on_unimplemented`
* `optin_builtin_traits`
* `plugin`
* `rustc_attrs`
* `rustc_diagnostic_macros`
* `slice_patterns`
In addition some feature gate error message typos fixed.
|
|
Okay, last chapter other than ownership stuff. :confetti_ball:
|
|
From https://github.com/rust-lang/rust/issues/24723#issuecomment-95636827 :
> Yes, I've been meaning to just remove it in favor of GRAMMAR.md
> - steveklabnik
|
|
r=alexcrichton
I forgot these heavily use associated types, so move it after that
as well.
|
|
r? @alexcrichton
|
|
Fixes #24656
r? @pnkfelix
I just added the examples, but if the wording needs expanded too, let me know what you think should be added :)
|
|
|
|
|
|
Fixes #24656
|
|
|
|
|
|
I forgot these heavily use associated types, so move it after that
as well.
|
|
Rather than storing the relations between free-regions in a global
table, introduce a `FreeRegionMap` data structure. regionck computes the
`FreeRegionMap` for each fn and stores the result into the tcx so that
borrowck can use it (this could perhaps be refactored to have borrowck
recompute the map, but it's a bid tedious to recompute due to the
interaction of closures and free fns). The main reason to do this is
because of #22779 -- using a global table was incorrect because when
validating impl method signatures, we want to use the free region
relationships from the *trait*, not the impl.
Fixes #22779.
|
|
|
|
|
|
|
|
|
|
why use dummy implementation on linux?
|
|
* `for` loops now use `IntoIterator` instead of just `Iterator`
* Simplify the example by removing unnecessary `Vec::iter` call.
|
|
|
|
Audit & Edit Chapter 8.1 Types in reference manual
- Remove mention of unit type
- Update closure types and reference types sections
- Fix minor typos
|
|
FIxes #24712
|
|
- Remove mention of unit type
- Update closure types and reference types sections
- Fix minor typos
|
|
It was in pretty good shape, but since that is my pet peeve, I clarified the compiler/interpreter distinction and why it is irrelevant for this section. Otherwise only a couple of minor clarifications, and weasel words where reality is more complicated than the text accounted for (e.g., there is more than one kind of library).
r? @steveklabnik
|
|
`us` and `is` were replaced with `usize` and `isize` some time ago. Other than that, 3.5.2.1.5 is correct.
|
|
r? @alexcrichton (since you added `.stability` warning messages)
|
|
`ToCStr` was removed with `old_io` and the current method `as_os_str`
is inherent to `Path`, meaning there is no suitable trait bound that
could be used here.
r? @alexcrichton
|
|
r? @steveklabnik
|
|
r? @steveklabnik
|
|
this is too small for its own thing, I think.
|
|
|
|
Changed in #22838.
audited (raw) byte string literals @ #16676
|
|
|
|
|
|
Add section for range expressions.
|
|
Updated sample code to updated syntax (now compiles). Also tweaked the text to reflect the change.
|
|
1) Moved 'while' section below 'loop', 'break', and 'continue'; 2) Added information to 'while' and 'for' loops that they interact with 'break' and 'continue' and may have a lifetime label. 3) Clarified labeling syntax on the infinite loops.
|
|
r? @steveklabnik
|
|
* Add two missing keywords, `Self` and `proc`
* Fix some mis-alphabetized keywords
r? @steveklabnik
|
|
r? @steveklabnik
|
|
(And other kinds of items).
This brings trait/impl items in line with top-level items in this respect. It means we don't get the attributes when showing error messages for methods, etc. (a good thing, I think). Since attributes have spans it is still easy to create a span for the item + all attributes.
|
|
'win32' -> 'windows', added 'ios'
|
|
Consistency. The book also refers to it as trait objects.
|
|
|