Skip to content

question about usage of unwrap() #27

@dataf3l

Description

@dataf3l

in past projects, I've found uses of unwrap() to be the quick and dirty solution to error propagation, this is great, because you can just "be done with it", however, when it breaks in production it is actually hard to figure out what happened some times, since lots of code investigation has to happen, and no explicit error message is written.
the question is, should this unwrap thing become a Result that propagates up the call stack? would that make the program messier?

https://github.com/sarahlim/wasm-trace/blob/796219b38f3b8df167c1d652f196a6365545950c/src/module.rs#L154

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions