Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename Receiver -> LegacyReceiver #130225

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Commits on Oct 15, 2024

  1. Rename Receiver -> LegacyReceiver

    As part of the "arbitrary self types v2" project, we are going to
    replace the current `Receiver` trait with a new mechanism based on a
    new, different `Receiver` trait.
    
    This PR renames the old trait to get it out the way. Naming is hard.
    Options considered included:
    * HardCodedReceiver (because it should only be used for things in the
      standard library, and hence is sort-of hard coded)
    * LegacyReceiver
    * TargetLessReceiver
    * OldReceiver
    
    These are all bad names, but fortunately this will be temporary.
    Assuming the new mechanism proceeds to stabilization as intended, the
    legacy trait will be removed altogether.
    
    Although we expect this trait to be used only in the standard library,
    we suspect it may be in use elsehwere, so we're landing this change
    separately to identify any surprising breakages.
    
    It's known that this trait is used within the Rust for Linux project; a
    patch is in progress to remove their dependency.
    
    This is a part of the arbitrary self types v2 project,
    rust-lang/rfcs#3519
    rust-lang#44874
    
    r? @wesleywiser
    adetaylor committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    20d50af View commit details
    Browse the repository at this point in the history