minor docs

Author: Quba1

src/codes_handle/mod.rs

@@ -50,25 +50,17 @@ impl<D: Debug> HandleGenerator for CodesFile<D> {
 /// - From GRIB index using [`new_from_index()`](CodesHandle::new_from_index) (with `experimental_index` feature enabled)
 ///
 /// Destructor for this structure does not panic, but some internal functions may rarely fail
-/// leading to bugs. Errors encountered in the destructor are logged with [`log`].
+/// leading to bugs. Errors encountered in the destructor are logged with [`tracing`].
 ///
-/// # `FallibleStreamingIterator`
+/// # `FallibleIterator`
 ///
-/// This structure implements [`FallibleStreamingIterator`](crate::FallibleStreamingIterator) trait which allows to access GRIB messages.
+/// This structure implements [`FallibleIterator`](crate::FallibleStreamingIterator) trait which allows to access GRIB messages.
 ///
 /// To access GRIB messages the ecCodes library uses a method similar to a C-style iterator.
 /// It digests the `* FILE` multiple times, each time returning the `*mut codes_handle`
-/// to a message inside the file. The behavior of previous `*mut codes_handle` after next one is generated is undefined
-/// and we assume here that it is unsafe to use "old" `*mut codes_handle`.
+/// to a message inside the file.
 ///
-/// In Rust, such pattern is best represented by a streaming iterator which returns a reference to the message,
-/// that is valid only until the next iteration. If you need to prolong the lifetime of the message, you can clone it.
-/// Internal ecCodes functions can fail, necessitating the streaming iterator to be implemented with
-/// [`FallibleStreamingIterator`](crate::FallibleStreamingIterator) trait.
-///
-/// As of `0.10` release, none of the available streaming iterator crates utilises already stabilized GATs.
-/// This unfortunately significantly limits the number of methods available for `CodesHandle` iterator.
-/// Therefore the probably most versatile way to iterate over the messages is to use `while let` loop.
+/// This behaviour is represented in this crate by `FallibleIterator`, because generating `KeyedMessage` can fail.
 ///
 /// ```
 /// use eccodes::{ProductKind, CodesHandle, KeyRead};