Re: [swift-evolution] Proposal: Add generator functions to the language

It'd be interesting to see if we can add some sort support for generator functions / yield functions to the language. As I believe we currently can only have a callback-style generator in which we have to manage the generator's state ourselves. It would be great to be able to use `yield` and no

Re: [swift-evolution] Publish shell completions scripts with the toolchain

Any ideas? Thanks, -- Bouke On 2017-07-04 05:28:42 +, Bouke Haarsma via swift-evolution said: My message's formatting got all messed up, here's my plain text re-post: Some time ago I've provided SwiftPM with shell completion scripts (see PR [#703][703]) for both Bash

Re: [swift-evolution] Publish shell completions scripts with the toolchain

My message's formatting got all messed up, here's my plain text re-post: Some time ago I've provided SwiftPM with shell completion scripts (see PR [#703][703]) for both Bash and ZSH. These completions are quite useful as shown in the following gifs; Bash: ![Bash][1] ZSH: ![ZSH][2] They are c

[swift-evolution] Publish shell completions scripts with the toolchain

Hi all, Some time ago I've provided SwiftPM with shell completion scripts (see PR #703 ) for both Bash and ZSH. These completions are quite useful as shown in the following gifs; ZSH: https://cloud.githubusercontent.com/assets/235882/18910

Re: [swift-evolution] Revisiting SE-0110

On 2017-05-24 19:12:14 +, Tony Parker via swift-evolution said: Hi everyone, We received a pull request in swift-corelibs-foundation which is apparently in response to a language change for SE-0110. It turns this perfectly reasonable code: -        self.forEach { (keyItem, valueItem) in

Re: [swift-evolution] [Pitch] Cross-platform Swift TLS library

Hi Gelareh, Overall I think this pitch is a great move forward. I've found that this is already resulting in some incompatibilities trying to combine rather complex Swift projects. I recently worked on integrating Kitura-Net, which uses BlueCryptor as a wrapper over both CommonCrypto / OpenS

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

On 2017-03-20 23:54:47 +, Douglas Gregor via swift-evolution said: • What is your evaluation of the proposal? -1. I share Drew Crawford's concerns regarding the proposal. -- Bouke___ swift-evolution mailing list swift-evolution@swif

Re: [swift-evolution] Plan to move swift-evolution and swift-users mailing lists to Discourse

A big +1 for Discourse from me as well. I don't want to sign up to the mailing list and have mailbox overflow. I did have rules put in place to move the messages in a separate folder, but still the amount wasn't manageable. Furthermore reading the threads in Mail.app is a major pain as a result

Re: [swift-evolution] [swift-build-dev] [Review] SE-0149 Package Manager Support for Top of Tree development

On 2017-01-24 20:28:30 +, Daniel Dunbar via swift-evolution said: I am reposting this since the URLs were mangled in the original email. Hello Swift community, The review of SE-0149 “ Package Manager Support for Top of Tree development" begins now and runs through January 31, 2017. The pr

Re: [swift-evolution] [Review] SE-0150 Package Manager Support for branches

On 2017-01-24 18:18:07 +, Daniel Dunbar via swift-build-dev said: Hello Swift community, The review of SE-0150 “ Package Manager Support for branches" begins now and runs through January 31, 2017. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/pro

Re: [swift-evolution] [Review] SE-0145: Package Manager Version Pinning (Revised)

On 2016-11-20 05:48:48 +, Anders Bertelrud via swift-build-dev said: * What is your evaluation of the proposal? Good. The revision is a good improvement over the original proposal. Build reproducability is great improvement to the ecosystem. * Is the problem being addressed signi

Re: [swift-evolution] Type-annotated throws

On 2016-08-26 15:39:05 +, Félix Cloutier via swift-evolution said: Hi all, Currently, a function that throws is assumed to throw anything. There was a proposal draft last December to restrict that. The general idea was that you'd write, for instance: enum Foo: ErrorProtocol {     case