[swift-evolution] higher kinded types vs Python's syntactic sugars

Austin Zheng austinzheng at gmail.com
Thu Dec 17 17:56:00 CST 2015

Different people are participating in different topics, so I wouldn't take
the different responses as indicative of the community's opinion as a whole.

Another thing: higher-kinded types would make it easier to implement the
sort of list comprehensions that languages like Scala have. The philosophy
of the language, as stated by multiple members of the core team, is to
prefer building tools that allow language features to be defined in
libraries, over hard-coding specific features into the language grammar and
specification. Here are a couple of examples:

- Custom operators and operator overloading, so things like '+' can be
defined in the standard library
- isUniquelyReferenced(), so that library developers can implement their
own collections with value semantics
- Literal convertible protocols, so that third-party types can be
initialized from literals in source code when it makes sense


On Thu, Dec 17, 2015 at 3:29 PM, Amir Michail via swift-evolution <
swift-evolution at swift.org> wrote:

> How is it possible that higher kinded types are being discussed seriously
> while Python’s syntactic sugars (e.g., comprehensions) have been dismissed
> as too confusing?
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151217/45449832/attachment.html>

More information about the swift-evolution mailing list