Rename Error::provide to Error::provide_context

[c4rtune]

Resolves the deref/autoref method name conflict between Error::provide and Provider::provide mentioned in the tracking issue for error_generic_member_access rust-lang/rust#99301.

Note: provide_context is the method name that was originally proposed in the RFC.

This comment suggests removing the provider API, which would also resolve the name conflict as a side effect. However, even if it is indeed removed, there's still a small chance it'll be brought back later, I guess. Plus, some users (including myself) feel like the name provide_context provides a clearer indication what should be provided.

[MonnetalX]

🔍 PR Link Analysis

🔗 Ranked Links

#1 RFC

🔍 Renaming Error::provide to Error::provide_context aligns with the original RFC proposal and provides clearer indication of what the method should provide.

#2 This comment

🔍 Renaming Error::provide to Error::provide_context resolves a method name conflict with Provider::provide and offers a clearer indication of what the method should provide.

#3 some users

🔍 Renaming Error::provide to Error::provide_context resolves a method name conflict with Provider::provide and provides a clearer indication of what should be provided.

#4 rust-lang/rust#99301

🔍 Renaming Error::provide to Error::provide_context resolves a method name conflict with Provider::provide and provides clearer indication of what should be provided.

#5 deref/autoref method name conflict

🔍 The method name provide_context was originally proposed in the RFC and provides a clearer indication of what should be provided, while also resolving the deref/autoref method name conflict between Error::provide and Provider::provide.