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

Added closing quotation mark #53

Merged
merged 1 commit into from Dec 3, 2015
Merged

Added closing quotation mark #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion www/FAQ.rst
View file
Open in desktop
Expand Up @@ -38,7 +38,7 @@ Won't the design and evolution of Swift be warped by being too C++-centric?

This is a common question from Objective-C programmers, primarily those who
really dislike C++. There are a lot of reasons you can have hope that Swift
will end up being a great "successor to Objective-C instead of a "C++
will end up being a great "successor to Objective-C" instead of a "C++
replacement":

* The compiler team has expert-level knowledge of Objective-C (the language),
Expand Down