-
-
Notifications
You must be signed in to change notification settings - Fork 235
Description
As of right now, it is quite difficult to trace through code to determine where "file not found" error messages are even coming from. This is because the string "file not found" does not appear in code, indicating the error likely comes from some dependency.
While trying to trace through and see what functions can fail, I noticed that we have several functions that cannot ever error, but which still return a
Result
. The existence of these functions makes it difficult to see what can actually fail in the code. Fortunately, we can enable theunnecessary_wraps
Clippy lint to find these functions. Before trying to improve the file not found error messages, it likely makes sense to enable this lint to make it easier for us to find where the file not found errors might occur.
Originally posted by @szokeasaurusrex in #2180