You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// Get a size hint for how many bytes out of an `Unstructured` this type
324
326
/// needs to construct itself.
325
327
///
326
-
/// Unlike [`size_hint`], this function keeps the information
327
-
/// that the recursion limit was reached. This is required to "short circuit" the calculation
328
-
/// and avoid exponential blowup with recursive structures.
328
+
/// Unlike [`size_hint`], this function keeps the information that the
329
+
/// recursion limit was reached. This is required to "short circuit" the
330
+
/// calculation and avoid exponential blowup with recursive structures.
329
331
///
330
-
/// If you are implementing [`size_hint`] for a struct that could be recursive, you should implement `try_size_hint` and call the `try_size_hint` when recursing
332
+
/// If you are implementing [`size_hint`] for a struct that could be
333
+
/// recursive, you should implement `try_size_hint` and call the
334
+
/// `try_size_hint` when recursing
331
335
///
332
336
///
333
-
/// The return value is similar to
334
-
/// [`Iterator::size_hint`][iterator-size-hint]: it returns a tuple where
335
-
/// the first element is a lower bound on the number of bytes required, and
336
-
/// the second element is an optional upper bound.
337
+
/// The return value is similar to [`core::iter::Iterator::size_hint`]: it
338
+
/// returns a tuple where the first element is a lower bound on the number
339
+
/// of bytes required, and the second element is an optional upper bound.
337
340
///
338
-
/// The default implementation return the value of [`size_hint`] which is correct for any
339
-
/// type, but might lead to exponential blowup when dealing with recursive types.
341
+
/// The default implementation returns the value of [`size_hint`] which is
342
+
/// correct for any type, but might lead to exponential blowup when dealing
0 commit comments