Skip to content

Conversation

Manishearth
Copy link
Member

I've never heard it pronounced "vector". Is this an outdated recommendation?

(or have I been doing it wrong all this time)

r? @steveklabnik

@frewsxcv
Copy link
Contributor

frewsxcv commented Jun 2, 2017

https://github.com/rust-lang/rust/search?l=Rust&q=vector&type=&utf8=%E2%9C%93

the term 'vector' gets used in a lot of places besides this. if we're going to remove this usage here, we should update other places

@Manishearth
Copy link
Member Author

Manishearth commented Jun 2, 2017

Right, but that's written as "vector". A Vec is a vector, just like an apple is a fruit. You don't say "fruit" when you read the word "apple". The question is how Vec is pronounced when in code written as Vec

@frewsxcv
Copy link
Contributor

frewsxcv commented Jun 2, 2017

The question is how Vec is pronounced when in code written as Vec

i personally do say 'vector'. though i'm apathetic about whether we encourage that or not

@kennytm
Copy link
Member

kennytm commented Jun 2, 2017

If the point is to introduce the word "vector", we would reword the sentence keep mentioning "vector" but eliminate the "pronunciation".

A contiguous growable array type with heap-allocated contents, commonly known as “vector” or “dynamic array”. In Rust this type is written as Vec<T>.

@shepmaster shepmaster added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 2, 2017
@shepmaster
Copy link
Member

FWIW, I'm a big fan of things describing how they are pronounced. (Like 'a is "tick a"). Adding some IPA to show how Vec is actually pronounced wouldn't make me sad 😺 .

@steveklabnik
Copy link
Contributor

It's both really, I'd say "vek t" for Vec<T> but also sometimes say "a vector."

@Manishearth
Copy link
Member Author

also sometimes say "a vector."

While reading code? For "a vector" my comment about "a fruit" applies 😄

@alexcrichton
Copy link
Member

ping @steveklabnik for review!

@steveklabnik
Copy link
Contributor

@bors: r+ rollup

@bors
Copy link
Collaborator

bors commented Jun 8, 2017

📌 Commit fdb2837 has been approved by steveklabnik

@est31
Copy link
Member

est31 commented Jun 8, 2017

so this chapter should be renamed to "vecs"? https://doc.rust-lang.org/book/vectors.html

@frewsxcv
Copy link
Contributor

frewsxcv commented Jun 8, 2017

so this chapter should be renamed to "vecs"? https://doc.rust-lang.org/book/vectors.html

why?

@Manishearth
Copy link
Member Author

Again, this doesn't make it not a "vector". It just means that you pronounce "Vec<T>" as "vec" in code. It's still a vector.

@est31
Copy link
Member

est31 commented Jun 8, 2017

I see, thanks!

frewsxcv added a commit to frewsxcv/rust that referenced this pull request Jun 8, 2017
Vec<T> is pronounced 'vec'

I've never heard it pronounced "vector". Is this an outdated recommendation?

(or have I been doing it wrong all this time)

r? @steveklabnik
bors added a commit that referenced this pull request Jun 8, 2017
Rollup of 6 pull requests

- Successful merges: #42307, #42385, #42487, #42491, #42521, #42531
- Failed merges:
frewsxcv added a commit to frewsxcv/rust that referenced this pull request Jun 9, 2017
Vec<T> is pronounced 'vec'

I've never heard it pronounced "vector". Is this an outdated recommendation?

(or have I been doing it wrong all this time)

r? @steveklabnik
bors added a commit that referenced this pull request Jun 9, 2017
Rollup of 5 pull requests

- Successful merges: #42307, #42385, #42531, #42551, #42558
- Failed merges:
@bors bors merged commit fdb2837 into rust-lang:master Jun 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants