Talk:Swift (programming language)
This is the talk page for discussing improvements to the Swift (programming language) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 6 months ![]() |
![]() | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Template:Vital article Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
|
Article reads like marketing material for Swift language lovers
Suggest rewrite to express Swift without the marketing angle. — Preceding unsigned comment added by 98.6.205.71 (talk) 05:22, 10 February 2020 (UTC)
Include discussion on performance or remove section
The section on performance is very short: "Many of the features introduced with Swift have well-known performance and safety trade-offs. Apple has implemented optimizations that reduce this overhead.[77]".
It leads to more questions than answers:
- What are the performance trade-offs?
List them! At least include some examples, even if they're supposed to be "well-known" (which is never substantiated with a citation). - What are the "well-known" safety trade-offs?
List them! Same issue as with performance trade-offs. - What is the overhead mentioned in the last sentence?
Since this section is only about performance, it should include at least a summary of the content from the citation. - What has apple done to reduce this overhead?
Shortly summarize the citation. - Is the overhead completely neutralized?
The sentence is completely worthless without knowing how much of that overhead has been compensated. This info is vital for users to decide whether the overhead is of concern.
Without tackling these issues, this whole section just sounds like: "Apple included stuff that is not good for performance or security, but we won't tell you what it is. Apple thought about these issues, so just trust them and assume that they fixed every problem without requiring any prove or explanation".
In short, this section contains as much information as the sentence "trust me, I'm an engineer".
Laciuhnf (talk) 15:49, 23 April 2021 (UTC)
Should "Kotlin" be a "Influenced by" entry?
Swift seems similar in terms of syntax to Kotlin. Take a look at this comparison: http://nilhcem.com/swift-is-like-kotlin/ Should "Kotlin" be a "Influenced by" entry? — Preceding unsigned comment added by 27.0.3.145 (talk) 08:12, 8 June 2017 (UTC)
No, influenced by languages / languages that Swift influenced need to come from official (from eg Swift designers), credible sources, not by an outsider's opinion how they think two languages are alike. We could for example add that Swift influenced Rust: https://doc.rust-lang.org/reference/influences.html — Preceding unsigned comment added by 2601:647:4801:626C:CD45:CED8:69BA:9221 (talk) 17:49, 20 April 2019 (UTC)
A Commons file used on this page or its Wikidata item has been nominated for deletion
The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:
Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 03:53, 18 April 2020 (UTC)
Potential error in paragraph under "Basic Syntax" section
After the third code block in the Basic Syntax section, there's a paragraph beginning:
else
statements require that the given condition is true...
From the context surrounding that paragraph, I feel like references to
should instead be references to else
statements
, but I don't know enough about Swift to be sure. Could someone passing by with more knowledge of Swift please confirm? KCastellino talk 15:35, 24 October 2023 (UTC)
guard
statements
- All unassessed articles
- B-Class Technology articles
- WikiProject Technology articles
- B-Class Computing articles
- High-importance Computing articles
- All Computing articles
- B-Class Apple Inc. articles
- High-importance Apple Inc. articles
- WikiProject Apple Inc. articles
- B-Class Computer science articles
- Mid-importance Computer science articles
- WikiProject Computer science articles