B Ohr writes:
@ericasadun just successfully created a symbolic link in the Sources folder of a playground to a swift file outside with Xcode 6.3.2
— B. Ohr (@J7zz) May 23, 2015
So I put it to the test.
Ages ago, I tried to convince Steve Sande to co-write a book just about Preview. I even spec’ed up a cover for it, as you see here.
Last night, I spent a tad more time on SourceKit parsing than any human would find reasonable. After, I looked what I had done, experienced shame, and ripped it all back out. Here is the story of my SourceKit.
Update: testlint now uses multiple
targets schemes (thanks Julien and Dan)
I hate dependencies. I don’t care what dependency manager you’ve signed onto, I probably don’t want to go there and do that.
I’ve recently switched the comment system from Disqus over to Jetpack. It should be less intrusive and friendlier (I hope!). However, in the move, I lost some comments.
Leaping from tree to tree! As they float down the mighty rivers of British Columbia! With my best girl by my side!
The Larch! The Pine! The Giant Redwood tree! The Sequoia!
The Little Whopping Rule Tree! We’d sing! Sing! Sing!
– The Lumberjack Song
Swift logging is a delightfully odd creature. Did you know, for instance, that there are separate standard and debugging logging features? Or that you could log directly to a string?
Here are a bunch of logging tips for you to enjoy.
There’s a lot to love about Swift. Here are 6 of my faves.
Clearing out my mailbox, this morning.
Fabio Virgi of Paddle.com sent over a PR kit for their new Mac app analytics package. With just a few lines of code, the embedded tools enable you to track how the app is being used, IAP conversions, etc. Fabio writes, “It’s totally free to use, and probably worth mentioning that it can be used for Mac App Store apps and those being independently distributed.” Not really anything I’d use but may be of interest to some of you out there.
Swift’s map functions provide elegant list processing that save you time when coding. Use them for good and not evil.
Today’s post on SwiftLint over at Natasha (The Robot) Murashev’s This Week in Swift inspired me to stop complaining abut lint issues and start building. While I love the idea behind SwiftLint, I didn’t entirely love the implementation or the rules.
I wanted something good enough to be used today with real code, even in imperfect form. It had to run from the command line and work with playgrounds. It had to be able to scan files added to Xcode projects by reference as well as those physically stored in the $SRCROOT.