move IntoFuture ahead of c-compatible ffi types

Author: pietroalbini

posts/2022-09-22-Rust-1.64.0.md

@@ -30,24 +30,6 @@ might come across!
 
 ## What's in 1.64.0 stable
 
-### C-compatible FFI types in core and alloc
-
-When calling or being called by C ABIs, Rust code can use type aliases like
-`c_uint` or `c_ulong` to match the corresponding types from C on any target,
-without requiring target-specific code or conditionals.
-
-Previously, these type aliases were only available in `std`, so code written
-for embedded targets and other scenarios that could only use `core` or `alloc`
-could not use these types.
-
-Rust 1.64 now provides all of the `c_*` type aliases in
-[`core::ffi`](https://doc.rust-lang.org/core/ffi/index.html), as well as
-[`core::ffi::CStr`](https://doc.rust-lang.org/core/ffi/struct.CStr.html) for
-working with C strings. Rust 1.64 also provides
-[`alloc::ffi::CString`](https://doc.rust-lang.org/alloc/ffi/struct.CString.html)
-for working with owned C strings using only the `alloc` crate, rather than the
-full `std` library.
-
 ### Enhancing `.await` with `IntoFuture`
 
 Rust 1.64 stabilizes the
@@ -140,6 +122,24 @@ This should make implementing `IntoFuture` easier by simplifying the type
 alias' signature, and make it more performant by removing the `Box` from the
 type alias.
 
+### C-compatible FFI types in core and alloc
+
+When calling or being called by C ABIs, Rust code can use type aliases like
+`c_uint` or `c_ulong` to match the corresponding types from C on any target,
+without requiring target-specific code or conditionals.
+
+Previously, these type aliases were only available in `std`, so code written
+for embedded targets and other scenarios that could only use `core` or `alloc`
+could not use these types.
+
+Rust 1.64 now provides all of the `c_*` type aliases in
+[`core::ffi`](https://doc.rust-lang.org/core/ffi/index.html), as well as
+[`core::ffi::CStr`](https://doc.rust-lang.org/core/ffi/struct.CStr.html) for
+working with C strings. Rust 1.64 also provides
+[`alloc::ffi::CString`](https://doc.rust-lang.org/alloc/ffi/struct.CString.html)
+for working with owned C strings using only the `alloc` crate, rather than the
+full `std` library.
+
 ### Stabilizing `ready!` and `poll_fn`
 
 When working with the low-level details of futures, you'll currently often