Skip to content

Commit

Permalink
Use monospace font for device indices
Browse files Browse the repository at this point in the history
  • Loading branch information
bdice authored Dec 5, 2024
1 parent 95ed8cb commit 492729a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -366,8 +366,8 @@ deallocation is performed (including in the destructor). The user must therefore
the device active during _creation_ of an `rmm::device_buffer` matches the active device of the
memory resource being used.

Here is an incorrect example that creates a memory resource on device 0 and then uses it to
allocate a `device_buffer` on device 1:
Here is an incorrect example that creates a memory resource on device `0` and then uses it to
allocate a `device_buffer` on device `1`:

```c++
{
Expand All @@ -381,7 +381,7 @@ allocate a `device_buffer` on device 1:
}
```

A correct example creates the device buffer with device 0 active. After that it is safe to switch
A correct example creates the device buffer with device `0` active. After that it is safe to switch
devices and let the buffer go out of scope and destruct with a different device active. For example,
this code is correct:

Expand Down

0 comments on commit 492729a

Please sign in to comment.