std::error::Error trait doc still talks about `cause()` #57056

Arnavion · 2018-12-22T01:50:28Z

Lines 43 to 48 in a9ff135

    
           /// The [`cause`] method is generally used when errors cross "abstraction 
        
           /// boundaries", i.e.,  when a one module must report an error that is "caused" 
        
           /// by an error from a lower-level module. This setup makes it possible for the 
        
           /// high-level module to provide its own errors that do not commit to any 
        
           /// particular implementation, but also reveal some of its implementation for 
        
           /// debugging via [`cause`] chains.

This should be updated to talk about source() instead.

The text was updated successfully, but these errors were encountered:

…ource, r=wesleywiser Change std::error::Error trait documentation to talk about `source` instead of `cause` Resolves rust-lang#57056

sfackler added the A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools label Dec 22, 2018

steveklabnik added the P-medium Medium priority label Dec 27, 2018

czipperz mentioned this issue Dec 29, 2018

Change std::error::Error trait documentation to talk about source instead of cause #57192

Merged

bors closed this as completed in #57192 Jan 12, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

std::error::Error trait doc still talks about `cause()` #57056

std::error::Error trait doc still talks about `cause()` #57056

Arnavion commented Dec 22, 2018

std::error::Error trait doc still talks about cause() #57056

std::error::Error trait doc still talks about cause() #57056

Comments

Arnavion commented Dec 22, 2018

std::error::Error trait doc still talks about `cause()` #57056

std::error::Error trait doc still talks about `cause()` #57056