Re: [swift-evolution] [Swift4] Mailing list vs. Forum

+1 for a forum or other editable medium. On Sat, Jul 30, 2016 at 4:55 PM Charles Srstka via swift-evolution < swift-evolution@swift.org> wrote: > +1 from me as well to anything that allows editing typos after posting. > > Charles > > On Jul 30, 2016, at 8:22 AM, Haravikk via swift-evolution < >

Re: [swift-evolution] [Pitch] Add `mapValues` method to Dictionary

Thanks Dave, I have to learn how to use all these mailing list tools :) Honza On Sun, May 22, 2016 at 8:24 PM Dave Abrahams via swift-evolution < swift-evolution@swift.org> wrote: > > on Sat May 21 2016, Honza Dvorsky wrote: > > > Hi Brent, > > > > thanks, I should

Re: [swift-evolution] [Pitch] Add `mapValues` method to Dictionary

Please correct me if I'm off here, but I quickly looked at the implementation of lazy collections/sequences, and I think it's because the goal is to keep the API of e.g. normal Array and a lazy Array the same, so that you don't actually have to know which one you're working with. But under the

Re: [swift-evolution] [Pitch] Add `mapValues` method to Dictionary

ion call "operator". I originally > wanted this in Swift but now wonder if the first option might be a better > way to accomplish the same goals. > > -Matthew > > > > >> On 21 May 2016, at 11:27, Honza Dvorsky via swift-evolution < >

Re: [swift-evolution] [swift-build-dev] [Review] SE-0085: Package Manager Command Names

I also use the word SwiftPM (this exact spelling) when referring to the project (sometimes swiftpm, but only among friends :) ). However I think we're talking about two things: 1. commonly used name for the tool (I use SwiftPM), 2. short alias to make triggering it on the command line easier (I

Re: [swift-evolution] [swift-build-dev] [Review] SE-0085: Package Manager Command Names

I agree with Rob and Ankit, with one detail: I'd expect `spm` to print the help section, instead of building (just like npm, nvm, gem, pod etc). On Tue, May 10, 2016 at 10:31 AM Ankit Agarwal via swift-evolution < swift-evolution@swift.org> wrote: > +1 to spm or swiftpm (in that order) > As a

Re: [swift-evolution] [Review] SE-0085: Package Manager Command Names

I agree with the review feedback so far, it's a good proposal. But just as David mentioned, I think a `spm` command, which would just be an alias for `swift package` would work really well. `spm build`, `spm test` all feel very in line with existing tools like gem, npm, pod etc. I think those ~3

Re: [swift-evolution] Proposal Discussion Thread: SwiftPM: Locking and Overriding Dependencies

Very happy this is coming! I really like the details of this proposal as well. Just one thing - having the `VersionLocks` in `Packages/VersionLocks` seems like a bad idea to me. Couple of hurdles right away - for people who don't want to check in their dependencies, we can't just add `Packages`

Re: [swift-evolution] [Rejected] SE-0009 Require self for accessing instance members

Hi all, since you mentioned: > Individuals or teams that feel that explicit “self.” is beneficial for their own code bases can enforce such a coding convention via tooling with the status quo. Are there any existing tools that already do that? I was hoping for a compiler flag where one could

Re: [swift-evolution] [Rejected] SE-0009 Require self for accessing instance members

tion@swift.org> wrote: > > > > > >> On Jan 6, 2016, at 6:17 AM, Honza Dvorsky via swift-evolution < > swift-evolution@swift.org> wrote: > >> > >> I remember this being discussed in the conversation about this proposal > and I haven't seen anyone