Jump to content

Talk:Swift (programming language)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by SineBot (talk | contribs) at 17:50, 20 April 2019 (Signing comment by 2601:647:4801:626C:CD45:CED8:69BA:9221 - "Should "Kotlin" be a "Influenced by" entry?: "). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Vital article

Swift is the bank infrastructure for messages/payments

See http://www.riksbank.se/sv/Finansiell-stabilitet/Finansiell-infrastruktur/System-i-den-svenska-infrastrukturen/SWIFT/ --Mats33 (talk) 00:27, 18 September 2016 (UTC)[reply]

Someone Should Check Struct Copy On Write

"To ensure that even the largest structs do not cause a performance penalty when they are handed off, Swift uses copy on write so that the objects are copied only if and when the program attempts to change a value in them. This means that the various accessors have what is in effect a pointer to the same data storage, but this takes place far below the level of the language, in the computer's memory management unit (MMU). So while the data is physically stored as one instance in memory, at the level of the application, these values are separate, and physical separation is enforced by copy on write only if needed.[46]"

I am just learning Swift, but I know MMU's and this makes no sense for a struct that is not larger than at least a page, which is larger than most structs. The reference [46] is a long video, I scanned through it but could find no mention of this. Someone who knows Swift might either find a better reference if this paragraph is true, remove this paragraph if it is false, or qualify it that it is only used for large structs if that is the case. 73.93.154.221 (talk) 01:47, 22 December 2016 (UTC)[reply]

Is this a sales promotion?

Is the preamble/intro section written by the Apple sales dept? — Preceding unsigned comment added by Hence Jewish Anderstein (talkcontribs) 17:25, 30 January 2017 (UTC)[reply]

@Hence Jewish Anderstein: Someone added a {{advert}} template to this article last year, and it's still here. I still don't see anything wrong with the lead section. Does anyone know why this cleanup tag was added to this article? Jarble (talk) 07:37, 16 May 2017 (UTC)[reply]

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)[reply]

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)[reply]

One language or several

Technically Swift isn't one programming language but a family of (to some level) incompatible languages. This due to the forwards compatibility that is assumed as a property in a developing programming language isn't really there. Swift have had large changes in even fundamental parts of the design while still being a young language. The most obvious comparison (in modern programming languages) is that of Python 2.x to 3.x however Python don't do that kind of incompatible forking often and did not as a young language unlike Swift.

I'll not make an edit noting this as I'm a bit biased however it should be mentioned at least; especially as the incompatible changes are common, obvious and seem to be part of the development philosophy. 2.248.146.217 (talk) 10:40, 24 September 2017 (UTC)[reply]