e75660dad3
In this new version of Arbitrary Self Types, we no longer use the Deref trait exclusively when working out which self types are valid. Instead, we follow a chain of Receiver traits. This enables methods to be called on smart pointer types which fundamentally cannot support Deref (for instance because they are wrappers for pointers that don't follow Rust's aliasing rules). This includes: * Changes to tests appropriately * New tests for: * The basics of the feature * Ensuring lifetime elision works properly * Generic Receivers * A copy of the method subst test enhanced with Receiver This is really the heart of the 'arbitrary self types v2' feature, and is the most critical commit in the current PR. Subsequent commits are focused on: * Detecting "shadowing" problems, where a smart pointer type can hide methods in the pointee. * Diagnostics and cleanup. Naming: in this commit, the "Autoderef" type is modified so that it no longer solely focuses on the "Deref" trait, but can now consider the "Receiver" trait instead. Should it be renamed, to something like "TraitFollower"? This was considered, but rejected, because * even in the Receiver case, it still considers built-in derefs * the name Autoderef is short and snappy. |
||
|---|---|---|
| .. | ||
| bad-builder.rs | ||
| bad-builder.stderr | ||
| ufcs-explicit-self-bad.rs | ||
| ufcs-explicit-self-bad.stderr | ||
| ufcs-partially-resolved.rs | ||
| ufcs-partially-resolved.stderr | ||
| ufcs-polymorphic-paths.rs | ||
| ufcs-qpath-missing-params.rs | ||
| ufcs-qpath-missing-params.stderr | ||
| ufcs-qpath-self-mismatch.rs | ||
| ufcs-qpath-self-mismatch.stderr | ||