If I need to take this question elsewhere, please point me to the right list.
I decided to take the dive this morning and give XCode9 beta and Swift 4 a try.
I’m tired of not being able to refactor.
There are two things that the importer is trying to commonly change that I’m
curious about:
1)
> On Jun 20, 2017, at 2:25 PM, Travis Griggs wrote:
>
>>
>> On Jun 20, 2017, at 7:02 AM, David Baraff via swift-users
>> > wrote:
>>
>> I posted this on Apple’s developer forums, and someone suggested trying this
> On Jun 20, 2017, at 7:02 AM, David Baraff via swift-users
> wrote:
>
> I posted this on Apple’s developer forums, and someone suggested trying this
> here.
> Basically, see https://forums.developer.apple.com/thread/80349
>
> On Jun 18, 2017, at 10:33 PM, Howard Lovatt via swift-users
> wrote:
>
> To me Angle is a unit with two common representations: radians and degrees.
> It's not an enum because it doesn't have two values, it has one value that
> you can view in two ways.
>
>
> On May 22, 2017, at 5:56 PM, Greg Power wrote:
>
> Hi Travis,
>
> I’m certainly not a core contributor, but I could point you to the rejection
> email for this proposal, which you might not have seen:
>
>
In my own project, I add some extensions to Data and other objects to make
building/parsing Data objects easier. Amongst others, I have extensions like
this:
func += (data:inout Data, string:String) {
data.append(string.data(using: .utf8)!)
}
func += (data:inout Data,
> On Apr 5, 2017, at 7:37 AM, Jon Shier via swift-users
> wrote:
>
> This was something that sounded like a good change but is extremely
> annoying in use. Once I get time I’m going to try writing an extension on
> Optional that generates a logDescription
Not sure if I got the "reply all" right… I’ll throw my 2c in.
I like mailing lists. I like them, because they let me choose the viewer that I
want to participate with(separation of presentation and data). I lose that with
a web forum. And there’s something valuable about actually forcing people
I’m currently refactoring some code (Swift 3.?, latest XCode), and I ended up
with the following:
func spansTSON() -> TSON {
var docs = self.spans.map() { $0.tson }
for (span, doc) in zip(self.spans, docs) {
if let datum =
> On Jan 30, 2017, at 3:19 PM, Travis Griggs wrote:
>
> I’m currently refactoring some code (Swift 3.?, latest XCode), and I ended up
> with the following:
>
> func spansTSON() -> TSON {
> var docs = self.spans.map() { $0.tson }
> for
The behavior of the following playground snippet surprised me:
var source = [10, 20, 30, 40]
var stream = source.makeIterator()
stream.next() // 10
stream.next() // 20
stream.forEach { (each) in
print("\(each)")
} // prints 30, 40 to the console
stream.next() // 30
stream.next() //
Upgrading to beta6 of Xcode8, I’ve read through various SE’s and made fixes as
appropriate, but the following behavior I didn’t catch an explanation as to why
its now an error where it was fine before.
In a ViewController, I have something that looks like:
var addButton = UIButton(type:
> On Aug 3, 2016, at 3:36 PM, Jon Shier wrote:
>
> If you think Date and Data look similar at a glance, wouldn’t NSDate and
> NSData? Or are you comparing this against your old Array type?
Fair question. I did think of that. I did actually port this code from
Objective C.
Chapter 1:
Coming from a Smalltalk background, I was enjoying added all kinds of
properties to basic number types, for example:
extension Double {
var rounded:Double {
return round(self)
}
}
Chapter 2:
I upgraded to XCode8Beta4 yesterday and firstly got to change all of
14 matches
Mail list logo