You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As much as I love Rust's Result type, to use it effectively requires that it is always used. If a function returns a Result<T, E>, the caller of said function must use the result of that function. If they fail to do this, then any errors are silently ignored.
TypeDoc's Result type suffers from this problem. A cursory search didn't turn up any simple way to add a lint rule requiring that it be used, so we need to move back to standard exceptions. This was the cause of #1237.
This should be a relatively simple change. Delete result.ts, see what TS yells about, then switch to returning values directly.
The text was updated successfully, but these errors were encountered:
As much as I love Rust's
Result
type, to use it effectively requires that it is always used. If a function returns aResult<T, E>
, the caller of said function must use the result of that function. If they fail to do this, then any errors are silently ignored.TypeDoc's
Result
type suffers from this problem. A cursory search didn't turn up any simple way to add a lint rule requiring that it be used, so we need to move back to standard exceptions. This was the cause of #1237.This should be a relatively simple change. Delete
result.ts
, see what TS yells about, then switch to returning values directly.The text was updated successfully, but these errors were encountered: