drop_ok 1.0.2

`.drop_ok` syntax sugar for `Result`. It's instead of `.map(|_|())`.
Documentation
  • Coverage
  • 66.67%
    2 out of 3 items documented1 out of 2 items with examples
  • Size
  • Source code size: 6.18 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1.03 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 9s Average build duration of successful builds.
  • all releases: 9s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • usagi/drop_ok
    1 1 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • usagi

drop_ok

  • This crate defines DropOk<E> trait and impl for Result.
  • DropOk<E> trait has .drop_ok(self) -> Result<(), E> function.
  • This is a syntax sugar for .map(|_|()).

Useful scene

fn some_function() -> Result<(), MyError>
{
 match switcher
 {
  pattern_a => some_task1().drop_ok()?
  pattern_b => some_task2().drop_ok()?
  pattern_c => some_task3()?
  pattern_d => some_task4()
  _ => ()
 }
}

fn some_task1()     -> Result<i8     , MyError> { /* abbr */ }
fn some_task2<'a>() -> Result<&'a str, MyError> { /* abbr */ }
fn some_task3()     -> Result<()     , MyError> { /* abbr */ }
fn some_task4() { /* abbr */ }
  • See also: <tests/test.rs>

Note

"I don't need it, because ..."

  • Yes, your are right to your world.
    • But, I tired to type/see .map(|_|()). So I'm happy with.drop_ok().

LICENSE

Author