> On Aug 21, 2017, at 3:55 PM, David Zarzycki wrote:
>
> The easiest way to start adding new features to an existing project is by
> cribbing from existing features that are sufficiently similar (at least
> enough to get started and see what fails to compile after some changes). For
> example,
Title: Report
[FAILURE] oss-swift-4.0-package-osx [#89]
Build URL:https://ci.swift.org/job/oss-swift-4.0-package-osx/89/
Project:oss-swift-4.0-package-osx
Date of build:Mon, 21 Aug 2017 12:36:26 -0500
Build duration:4 hr 55 min
Changes
No Changes
Hi All-
Tomorrow, we will be temporarily bringing down the CI, starting around 11 AM,
California time, in order to upgrade to the latest beta of Xcode 9 and the
associated SDKs. We will also be briefly locking master while we land some
source changes in support of the updated SDKs on both mast
Hi Jimmy,
I’d personally really like to see swift-format written entirely in Swift using
libSyntax. It’s really easy to perform common formatting tasks just by
modifying the trivia for each token you’re trying to check (like replacing new
lines before a brace with a space, per se).
Unfortunate
Hey Swift team,
We’ve been trying to build a linter in-house that can cover most of our rules
(https://github.com/linkedin/swift-style-guide).
Our current approach for retrieving the AST has been very similar to how your
swift-format tool works, but at the moment swift-format is a bit too barebo
Hi Daryle,
The easiest way to start adding new features to an existing project is by
cribbing from existing features that are sufficiently similar (at least enough
to get started and see what fails to compile after some changes). For example,
if you wanted to implement a new and awesome loop co
I downloaded (w/ GitHub Desktop on macOS) a copy of the Swift repository. I ran
the build scripts to download the other parts of LLVM, built everything, and
created Xcode (9 beta 4) project files. Now how do I actually do a new feature?
The number of targets in the Xcode project file is so intim
