From e73c7959673ec4d64bdd059a78de4c8aca4aed4a Mon Sep 17 00:00:00 2001 From: Joseph Perez Date: Thu, 7 Dec 2023 10:10:15 +0100 Subject: [PATCH] docs: fix typos --- guide/src/SUMMARY.md | 4 ++-- guide/src/async-await.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/guide/src/SUMMARY.md b/guide/src/SUMMARY.md index 9e738a79..34775a0d 100644 --- a/guide/src/SUMMARY.md +++ b/guide/src/SUMMARY.md @@ -15,8 +15,8 @@ - [Emulating numeric types](class/numeric.md) - [Emulating callable objects](class/call.md) - [Type conversions](conversions.md) - - [Mapping of Rust types to Python types](conversions/tables.md)] - - [Conversion traits](conversions/traits.md)] + - [Mapping of Rust types to Python types](conversions/tables.md) + - [Conversion traits](conversions/traits.md) - [Python exceptions](exception.md) - [Calling Python from Rust](python_from_rust.md) - [Using `async` and `await`](async-await.md) diff --git a/guide/src/async-await.md b/guide/src/async-await.md index 847fed2f..9a517ecf 100644 --- a/guide/src/async-await.md +++ b/guide/src/async-await.md @@ -30,7 +30,7 @@ Resulting future of an `async fn` decorated by `#[pyfunction]` must be `Send + ' As a consequence, `async fn` parameters and return types must also be `Send + 'static`, so it is not possible to have a signature like `async fn does_not_compile(arg: &PyAny, py: Python<'_>) -> &PyAny`. -However, there is an exception for method receiver, so async methods can accept `&self`/`&mut self` +However, there is an exception for method receiver, so async methods can accept `&self`/`&mut self`. ## Implicit GIL holding