Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

On Sat, Oct 29, 2016 at 8:42 PM, Jonathan Hull wrote: > > On Oct 29, 2016, at 2:56 PM, Xiaodi Wu wrote: > > On Sat, Oct 29, 2016 at 4:14 PM, Jonathan Hull wrote: > >> >> On Oct 29, 2016, at 8:11 AM, Xiaodi Wu wrote: >>

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

> On Oct 29, 2016, at 2:56 PM, Xiaodi Wu wrote: > > On Sat, Oct 29, 2016 at 4:14 PM, Jonathan Hull > wrote: > >> On Oct 29, 2016, at 8:11 AM, Xiaodi Wu > > wrote: >> >> However,

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

On Sat, Oct 29, 2016 at 4:14 PM, Jonathan Hull wrote: > > On Oct 29, 2016, at 8:11 AM, Xiaodi Wu wrote: > > However, *my* main point is that the Swift's standard library APIs (and > the keywords and syntax at the core of the language) should use a character

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

> On Oct 29, 2016, at 8:11 AM, Xiaodi Wu wrote: > > However, *my* main point is that the Swift's standard library APIs (and the > keywords and syntax at the core of the language) should use a character set > that *requires no discovery whatsoever* for the vast majority of

Re: [swift-evolution] [Pitch] Reimagining guard case/if case

I'd like to write a proposal for "matches" and wonder if it is in Swift 4 Phase 1 scope? It's purely syntactic, and won't affect ABI. ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

On Sat, Oct 29, 2016 at 2:02 AM, Jonathan Hull wrote: > > On Oct 28, 2016, at 7:22 PM, Xiaodi Wu wrote: > > A person should not need to buy a special keyboard or device, or know how > to work the option/alt key, in order to write the less-than-or-equal-to >

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

Eh, I'm all for better emoji support but I think this needs to come in at the OS level. Part of the problem for emoji is that the macOS special characters menu is so awkward to use; coincidentally I actually posted an enhancement request to the Apple bug reporter only yesterday asking for a

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

> On Oct 29, 2016, at 12:40 AM, Rien wrote: > > Hmm, I have engineering problems today. There will be engineering problems in > 20 and 30 years as well, but I rather have a tool that is geared towards > today’s problems. It would be even better if that tool is flexible

Re: [swift-evolution] Promises, Futures and the death of the callback hell

I have quite high hopes for this subject, especially with all the work going into LLVM to support it from the ground up. Sent from my iPhone > On 29 Oct 2016, at 01:47, Xiaodi Wu via swift-evolution > wrote: > > Async and related topics are deferred until the

Re: [swift-evolution] guard let x = x

> On Oct 26, 2016, at 10:37 AM, Chris Lattner via swift-evolution > wrote: > > To me, this is the most promising direction, but I’d suggest the use of > “unwrap" as the keyword. If you compare these two: > > a) guard let foobar = foobar else { … } > b) guard

Re: [swift-evolution] [pitch] rename 'guard' to 'ensure'

Sent from my iPhone > On Oct 27, 2016, at 17:53, Charles Srstka via swift-evolution > wrote: > > As long as we’re considering Ensure, how about Depends? It will keep optional > values from leaking out. +1 ___

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

> > Swift is a language being designed for the next 20-30 years, we shouldn’t be > limiting ourselves based on technology that is already being replaced (as you > mentioned many of the devices people use everyday already have a soft > keyboard… and Ive said the TouchBar was just the beginning

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

There are people out there who insist on using spaces for indention, just because of fear that some odd editor might not be able to deal with tabs properly… so even if this idea doesn't require a TouchBar, I don't think we should replace words with somewhat exotic characters: Swift code will be

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

> On Oct 28, 2016, at 7:22 PM, Xiaodi Wu wrote: > > A person should not need to buy a special keyboard or device, or know how to > work the option/alt key, in order to write the less-than-or-equal-to operator. But my main point is that the symbols painted on the physical

Re: [swift-evolution] guard let x = x

+1 Can “unwrap” be used anywhere else? If not, why not remove the “guard” altogether? I.e. unwrap foobar else { … } Regards, Rien Site: http://balancingrock.nl Blog: http://swiftrien.blogspot.com Github: http://github.com/Swiftrien Project: http://swiftfire.nl > On 29 Oct 2016, at 00:34,

Re: [swift-evolution] [Meta] Let's talk TouchBar + Unicode

> On 29 Oct 2016, at 04:22, Xiaodi Wu via swift-evolution > wrote: > > The other has to do with expanding Swift standard library and core library > APIs beyond the ASCII character set. I'm -1 on that for the reasons I've > outlined above. Reworded, a very good