Rust 匹配结果时的简洁日志(log)记录

您可以使用.ok()将Result转换为Option，然后使用?传播它.

可以使用.map_err()来记录每个结果，以便对错误应用"转换".使用.inspect_err()(稳定后)或.tap_err()(来自tap箱)可能会稍好一些，但由于在记录后不会使用错误，因此这并不重要:

fn pathway_1(x: &str, y: &str) -> Option<Vec<String>> {
    let unique_numbers = query_unique_numbers(&x, &y)
        .map_err(|e| { log::error!(target: "normal", "Could not query unique numbers. Err {e}"); })
        .ok()?;

    let unique_people = query_unique_people(&unique_numbers, &y)
        .map_err(|e| { log::error!(target: "normal", "Could not query unique people. Err {e}"); })
        .ok()?;

    let relevant_things_by_people = query_relevant_things(&unique_people, &y)
        .map_err(|e| { log::error!(target: "normal", "Could not query relevant things. Err {e}"); })
        .ok()?;

    /// Many such function calls below.

    Some(vector_of_strings)
}

然而，我不会这样做的.您似乎在返回类型中使用了Option来表示失败.如果是这样的话，您应该返回Result.如果这样做，您可以创建一个适当的包含错误类型，它可以表示哪个步骤失败了，原始错误是什么，以及显示逻辑(使用类似thiserror箱的内容):

use thiserror::Error;

#[derive(Error, Debug)]
enum QueryError {
    #[error("Could not query unique numbers. Err {0}")]
    UniqueNumbers(SomeError),
    #[error("Could not query unique people. Err {0}")]
    UniquePeople(SomeError),
    #[error("Could not query relevant things. Err {0}")]
    RelevantThings(SomeError),
}

fn pathway_1(x: &str, y: &str) -> Result<Vec<String>, QueryError> {
    let unique_numbers = query_unique_numbers(&x, &y)
        .map_err(QueryError::UniqueNumbers)?;

    let unique_people = query_unique_people(&unique_numbers, &y)
        .map_err(QueryError::UniquePeople)?;

    let relevant_things_by_people = query_relevant_things(&unique_people, &y)
        .map_err(QueryError::RelevantThings)?;

    /// Many such function calls below.

    Ok(vector_of_strings)
}

然后，您可以在调用方的一个位置处理所有错误.例如:

match pathway_1(x, y) {
    Ok(vector_of_strings) => {
        // do something
    }
    Err(e) => {
        log::error!(target: "normal", "{e}");
    }
}