Is there an elegant way to handle None with a type that cannot be inferred?

The author discusses challenges in designing a flexible API function that uses an optional observer for progress reporting. They encounter type inference issues when trying to pass `None` as an argument, consequently exploring potential solutions such as creating a `NoneObserver` type, but find it unintuitive. The post raises questions about the design patterns of optional parameters in Rust and seeks advice on better approaches.