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

doc: add a new language design faq #14370

Merged
merged 1 commit into from
May 25, 2014
Merged

doc: add a new language design faq #14370

merged 1 commit into from
May 25, 2014

Conversation

emberian
Copy link
Member

This indends to help quell frequently answered questions about the language
design in a single, authoritative place.

@emberian
Copy link
Member Author

cc @brson @steveklabnik @sfackler (people who reviewed the draft)

@kud1ing kud1ing mentioned this pull request May 23, 2014
@kud1ing
Copy link

kud1ing commented May 23, 2014

@cmr: Awesome. Have you browsed #4047 for inspiration?

@emberian
Copy link
Member Author

@kud1ing This isn't meant to close #4047, but serve as a starting point for actually frequently-asked questions, based on my observations in IRC, rather than a catch-all.


### `struct`s

In a Rust long-gone, `struct` layout was defined to be the same as C. Now, they
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"long-gone"... 3 days ago :P

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs are forever!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Speaking of this, I feel really strongly that docs should be written in the present. I'd remove this whole first line.

@huonw
Copy link
Member

huonw commented May 23, 2014

Also, this needs makefile changes.

change. One main benefit is that, when indexing arrays, having a pointer-sized
index type lets you address the entire address space.

## No guaranteed Tail-call optimization
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be "tail-call" with a small t?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, given that the rest of the headings aren't in title case.

@emberian
Copy link
Member Author

I believe I have addressed all review. @steveklabnik I've addressed the reddit comment by linking to the ML post by graydon which lays out the same concern.

This document outlines some design decisions in the Rust language and why they
were made. Many of these are things that will not change. Unless you have an
extremely compelling argument that isn't presented here, proposing they be
changed is a waste of everyone's time. Many of these have technical
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"waste of everyone's time" is unnecessarily harsh. I'd say, instead:

"These decisions were arrived at after lengthy discussion and experimenting with alternatives. Please do not propose reversing them unless you have a new, extremely compelling argument."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree about the tone here.

@emberian
Copy link
Member Author

I've removed the section on exceptions and int/uint. I don't have strong answers for them, and I can envision them possibly changing.

This indends to help quell frequently answered questions about the language
design in a single, authoritative place.
bors added a commit that referenced this pull request May 25, 2014
This indends to help quell frequently answered questions about the language
design in a single, authoritative place.
@bors bors closed this May 25, 2014
@bors bors merged commit 11c0f77 into rust-lang:master May 25, 2014
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.