| Age | Commit message (Collapse) | Author | Lines |
|
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.
|
|
|
|
This can be specified using `extern sysV64 fn` on all platforms
|
|
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
|
|
The spacing seems inconsistent with existing style conventions.
|
|
Ensure that attributes are spelled properly.
|
|
|
|
|
|
The hidden find() functions always returns None. Consequently, one of the
examples using find() prints "No file extension found" instead of
"File extension: rs" which is the expected output.
This patch fixes the issue by implementing find() with std::str::find().
Signed-off-by: Christophe Vu-Brugier <cvubrugier@fastmail.fm>
|
|
|
|
|
|
book: fix formatting of module layout example
|
|
When using Point { x: 0, y: 0 } and showing pattern matching decomposing
x and y individually its hard to understand. By using a different value
for x and a different value for y it is more clear.
|
|
|
|
Update the-stack-and-the-heap.md
Was surprised to learn that heaps were used in this way, then realized upon reading [the linked paper](http://www.cs.cmu.edu/afs/cs/academic/class/15213-f98/doc/dsa.pdf) that it's a totally different type of heap—an important distinction.
|
|
Provide more explicit example of wildcard version in guessing game doc.
Beginners may try to adapt the tutorial to develop their own code.
When using different dependencies, they may use the wildcard for
versioning. Since they are new to the language, they will not know
that the wildcard asterisk is a string, not a token. Make the correct
format more explicit, to remove one potential source of frustration.
|
|
Was surprised to learn that heaps were used in this way, then realized upon reading [the linked paper](http://www.cs.cmu.edu/afs/cs/academic/class/15213-f98/doc/dsa.pdf) that it's a totally different type of heap—an important distinction.
|
|
|
|
Beginners may try to adapt the tutorial to develop their own code.
When using different dependencies, they may use the wildcard for
versioning. Since they are new to the language, they will not know
that the wildcard asterisk is a string, not a token. Make the correct
format more explicit, to remove one potential source of frustration.
|
|
Properly feature gate all unstable ABIs
Fixes https://github.com/rust-lang/rust/issues/34900
[breaking-change]
r? @pnkfelix
---
Function-visiting machinery for AST/HIR is surprisingly error-prone, it's *very* easy to miss some cases or visit something twice while writing a visitor. This is the true problem behind https://github.com/rust-lang/rust/issues/34900. I'll try to restructure these visitors a bit and send one more PR later.
|
|
Try to clear up some awkward wording
|
|
|
|
even though that is how it works
|
|
|
|
|
|
|
|
|
|
Not sure the example is going to stay, but I can try to pass Travis for the bragging rights.
|
|
|
|
|
|
|
|
|
|
|
|
Expand the "nullable pointer optimization" section with a code example.
Change examples to use std::os::raw instead of libc, when applicable.
|
|
doc/book/trait-objects: remove empty lines at start of examples
I think it looks better without them.
|
|
|
|
|