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

book: Change 'unified function call syntax' to 'associated item loookup syntax' #25965

Closed
wants to merge 1 commit into from

Conversation

nham
Copy link
Contributor

@nham nham commented Jun 2, 2015

see rust-lang/rfcs#1140

One issue is that this still doesn't have any examples of lookup of items that aren't associated with traits.

@rust-highfive
Copy link
Collaborator

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@nham
Copy link
Contributor Author

nham commented Jun 2, 2015

r? @steveklabnik

@steveklabnik
Copy link
Member

UFCS, while not a perfect name, is generally the name for this kind of thing. Creating a brand new term with an awkward name is 👎, as far as I'm concerned.

That doesn't mean that I'm totally opposed, but I think that we need a good reason to deviate here.

@nham
Copy link
Contributor Author

nham commented Jun 2, 2015

I'm not completely sold on "Associated Item Lookup Syntax", but the name is not really the major point here. The main thing I'm interested in pointing out in the docs is that "UFCS" syntax is not limited to function calls, but also works for associated types and constants. However, adding such a note to the UFCS chapter without changing the name seems to not work: if it's not limited to function calls, why introduce the 'UFCS' terminology?

Could the chapter title be "Lookup Disambiguation Syntax" instead? Perhaps the chapter could still mention that in the case of function calls, the syntax is sometimes called UFCS.

@bluss
Copy link
Member

bluss commented Jun 5, 2015

Core team discussed naming things: (notes)

@steveklabnik
Copy link
Member

Yes, I think that we are not going to be pursuing this particular approach forward, though I do think that it should be changed. I would prefer to see the UFCS chapter just disappear, and have this syntax be explained along with other function stuff, as the last part of that note mentions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants