mirror of
https://github.com/google/comprehensive-rust.git
synced 2025-03-21 14:46:37 +02:00
Remove the phrase "third-party" (#2512)
"Third-party" is a Googleism that doesn't make much sense otherwise. Most references to crates just say "crate", implying that they are open-source packages available on https://crates.io, so this updates a few additional locations to do the same.
This commit is contained in:
parent
fbeef48c50
commit
de8ae4fe08
@ -9,9 +9,9 @@ To use `alloc` you must implement a
|
|||||||
|
|
||||||
<details>
|
<details>
|
||||||
|
|
||||||
- `buddy_system_allocator` is a third-party crate implementing a basic buddy
|
- `buddy_system_allocator` is a crate implementing a basic buddy system
|
||||||
system allocator. Other crates are available, or you can write your own or
|
allocator. Other crates are available, or you can write your own or hook into
|
||||||
hook into your existing allocator.
|
your existing allocator.
|
||||||
- The const parameter of `LockedHeap` is the max order of the allocator; i.e. in
|
- The const parameter of `LockedHeap` is the max order of the allocator; i.e. in
|
||||||
this case it can allocate regions of up to 2**32 bytes.
|
this case it can allocate regions of up to 2**32 bytes.
|
||||||
- If any crate in your dependency tree depends on `alloc` then you must have
|
- If any crate in your dependency tree depends on `alloc` then you must have
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
# `buddy_system_allocator`
|
# `buddy_system_allocator`
|
||||||
|
|
||||||
[`buddy_system_allocator`][1] is a third-party crate implementing a basic buddy
|
[`buddy_system_allocator`][1] is a crate implementing a basic buddy system
|
||||||
system allocator. It can be used both for [`LockedHeap`][2] implementing
|
allocator. It can be used both for [`LockedHeap`][2] implementing
|
||||||
[`GlobalAlloc`][3] so you can use the standard `alloc` crate (as we saw
|
[`GlobalAlloc`][3] so you can use the standard `alloc` crate (as we saw
|
||||||
[before][4]), or for allocating other address space. For example, we might want
|
[before][4]), or for allocating other address space. For example, we might want
|
||||||
to allocate MMIO space for PCI BARs:
|
to allocate MMIO space for PCI BARs:
|
||||||
|
@ -46,7 +46,7 @@ Rust's ownership and borrowing model can, in many cases, get the performance of
|
|||||||
C, with alloc and free operations precisely where they are required -- zero
|
C, with alloc and free operations precisely where they are required -- zero
|
||||||
cost. It also provides tools similar to C++'s smart pointers. When required,
|
cost. It also provides tools similar to C++'s smart pointers. When required,
|
||||||
other options such as reference counting are available, and there are even
|
other options such as reference counting are available, and there are even
|
||||||
third-party crates available to support runtime garbage collection (not covered
|
crates available to support runtime garbage collection (not covered in this
|
||||||
in this class).
|
class).
|
||||||
|
|
||||||
</details>
|
</details>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user