| Age | Commit message (Collapse) | Author | Lines |
|
Note that attributes on expressions are still unstable and are behind the `stmt_expr_attributes` flag.
cc [Tracking issue](https://github.com/rust-lang/rust/issues/15701)
|
|
Docs: Update to "Getting Started" section
I came across #34523 and wanted to suggest a solution. See commit for details.
It seemed like a good place to start contributing, let me know if I did anything wrong 😇
|
|
|
|
Docs: Update to "Ownership" section
Found #34865 while looking for easy docs wins I could contribute with.
|
|
- Reword
- Add link
|
|
- Updated paragraphs and wording for clarity.
- Renamed `helloworld.rs` to `myprogram.rs` to make it clearer that it's an unrelated example.
|
|
|
|
|
|
book: fix mistake (File::open -> File::create)
|
|
book: fix a typo
|
|
|
|
|
|
Fixed typo in nomicon
|
|
|
|
add static_in_const feature gate
also updates tests and deletes the spurious .bk files I inadvertently added last time.
r? @nikomatsakis
|
|
|
|
|
|
|
|
|
|
Update nightly docs supported Windows versions to match Getting Started page
https://doc.rust-lang.org/book/getting-started.html#tier-1 shows that Windows 7+ is officially supported (implying, for example Windows 10), but the nightly page only listed 7, 8, and Server 2008 R2).
|
|
Add `must_use` to the Reference
I'm a bit uncertain about the exact phrasing, but having it mentioned at all is probably better than before.
|
|
|
|
Allow specification of the system V AMD64 ABI constraint.
This can be specified using `extern "sysV64" fn` on all platforms.
This ABI is used as the C ABI on unix platforms, but can only be specified there using extern "C". It was impossible to specify on other platforms. Meanwhile the win64 ABI, which was the extern "C" ABI on the windows platform could be specified on other platforms using extern "win64".
This pull request adds the the "sysV64" ABI constraint which exposes this calling convention on platforms where it is not the C ABI.
|
|
and add the feature(abi_sysv64) to the list of known features
|
|
|
|
This can be specified using `extern sysV64 fn` on all platforms
|
|
Updated code sample in chapter on syntax extensions.
The affected API apparently had changed with commit d59accfb065843d12db9180a4f504664e3d23ef1.
---
Further more I had to add
```toml
[lib]
name = "roman_numerals"
crate-type = ["dylib"]
```
to `Cargo.toml` as I otherwise got this compiler error (despite `#![crate_type="dylib"]`):
[E0457]: plugin `roman_numerals` only found in rlib format, but must be available in dylib format
Might be worth adding a note about that?
|
|
We originally imported this into the repository with the intent of
fixing it up. Instead, nothing happened.
Its appearance on rust-lang.org makes it seem semi-official, but it's
not. The rustfmt strike team will end up producing something like this
anyway, and leaving it around does nothing but mislead people.
|
|
reference: add trailing commas
|
|
The affected API apparently had changed with commit d59accfb065843d12db9180a4f504664e3d23ef1.
|
|
Mark panicking tests as `should_panic` instead of `no_run`.
None
|
|
|
|
|
|
|
|
|
|
Fix minor typo
Minor typo in the book.
|
|
Very minor spelling fix in the book
Changed datastructure to data structure.
r? @steveklabnik
|
|
|
|
Changed datastructure to data structure
|
|
|
|
|
|
Fix spacing in code of closures.md
The spacing seems inconsistent with existing style conventions.
|
|
Improve `No stdlib` and related Documentation
This renames all lang item function names to the ones used in `libstd` and `libpanic_unwind`. It also explains the `eh_unwind_resume` lang item in the `libcore` documentation, where it was missing. A third function is also needed on certain compilation targets, so this was also added to the `No stdlib` documentation.
|
|
Clarify type declaration language in Associated Types docs
A small fix for the Associated Types docs
r? @steveklabnik
|
|
A disclaimer about keywords.
Some people cite this list as "zomg Rust has so many keywords," so make
it clear that these aren't all used by the language today.
|
|
Some people cite this list as "zomg Rust has so many keywords," so make
it clear that these aren't all used by the language today.
|
|
The spacing seems inconsistent with existing style conventions.
|
|
Ensure that attributes are spelled properly.
|
|
|
|
|