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.

Sign up for GitHub

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

Jump to bottom

consider selecting a matching name for like and ImplicitAs #1177

Open
zygoloid opened this issue Apr 8, 2022 · 1 comment
Open

consider selecting a matching name for like and ImplicitAs #1177

zygoloid opened this issue Apr 8, 2022 · 1 comment
Labels
long term Issues expected to take over 90 days to resolve.

Comments

@zygoloid
Copy link
Contributor

zygoloid commented Apr 8, 2022

As a mnemonic device, it may be useful to use the same spelling for like and the corresponding interface ImplicitAs, just as we use the same spelling for as and the corresponding interface As.

We should decide if we want to do this and pick what names we want:

  • like/Like: impl StringRef as Like(String) and impl like String as Add(like String)
  • implicit_as/ImplicitAs: impl StringRef as ImplicitAs(String) and impl implicit_as String as Add(implicit_as String)
  • implicitly/Implicitly: impl StringRef as Implicitly(String) and impl implicitly String as Add(implicitly String)
  • Something else. Suggestions please!
@chandlerc chandlerc added the long term Issues expected to take over 90 days to resolve. label Apr 8, 2022
@chandlerc
Copy link
Contributor

To clarify, this is a low-priority issue just to track revisiting the name at some point. It shouldn't block anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
long term Issues expected to take over 90 days to resolve.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zygoloid @chandlerc