[swift-evolution] [Review] SE-0006 Apply API Guidelines to the Standard Library

Charles Kissinger crk at akkyra.com
Wed Jan 27 17:08:51 CST 2016

> On Jan 27, 2016, at 1:57 PM, Radosław Pietruszewski <radexpl at gmail.com> wrote:
> But don’t you think any relative advantage of “require” is overshadowed by the potential for confusion since “require” means something completely different in *a lot* of other languages?

A valid concern. I’m glad I don’t have to be the one making the call on this. ;-)

My gut feeling is that the two uses are *so* different that it might not be a big issue for anybody. I would only worry about confusion when there is a subtle difference in how a keyword or function is used. An assert() call that is still active in release builds would surprise a lot of people. A very different use for a common word like 'require’ might not.


> — Radek
>> On 27 Jan 2016, at 22:56, Charles Kissinger via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> ‘Precondition’ is not particularly bad jargon since it is a standard dictionary word that is used with a similar meaning in areas outside of computer science. ‘Require’ probably has an advantage with students and non-native English speakers by virtue of being a much more commonly used and understood word.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160127/e415ed52/attachment.html>

More information about the swift-evolution mailing list