Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Hi Joe, Please ignore the swift-2.2-branch for now. Main development is happening on 'master'. The swift-2.2-branch will be used as the release branch for Swift 2.2. Details will be sent out soon, but right now the branch is in a bring up stage to work with a specific version of Clang. Chee

Re: [swift-dev] bugs.swift.org usage

> On Dec 21, 2015, at 11:17 AM, Chris Lattner via swift-dev > wrote: > > >> On Dec 21, 2015, at 8:31 AM, William Dillon via swift-dev >> wrote: >> >> Now that I’ve published a tarball of the ARM swift compiler, I’m getting >> some messages about this or that not working. I’m curious abou

Re: [swift-dev] Radar and bugs.swift.org

> On Dec 31, 2015, at 12:03 PM, Joe Groff via swift-dev > wrote: > > >> On Dec 31, 2015, at 11:47 AM, Keith Smiley via swift-dev >> wrote: >> >> Would it be worthwhile for the swift team if those of us who have created >> many swift related radars to copy them over to bugs.swift.org? > >

Re: [swift-dev] Swift vim support

Hi Keith, This makes complete sense. I can see why cloning a small self-contained repository would be ideal for plugin managers. I'll talk about this with the core team, but I think this seems like a reasonable direction. Incidentally, we would need one (or more) active maintainers for the vi

[swift-dev] Swift 2.2 release process

I have posted a blog post to Swift.org that documents the official release process for Swift 2.2: https://swift.org/blog/swift-2-2-release-process/ Please feel free to email this list or me directly questions about the process. In a nutshell: Swift 2.2 is a mostly source-compatible release

Re: [swift-dev] How to remove Swift Dev snapshot (OS X)

That is the correct way to do it. Everything should be in that folder. > On Jan 6, 2016, at 5:27 AM, Ryan Lovelett via swift-dev > wrote: > > I ended up running: > > cd /Library/Developer/Toolchains > sudo rm -rf swift-2.2-SNAPSHOT-2015-12-* swift-latest.xctoolchain > > Hopefully that remo

Re: [swift-dev] Documentation

Hi James, We're interested in hosting documentation on Swift.org for a variety of reasons. One motivating reason is to showcase the documentation for the version of the Standard Library that is in active development on 'master'. For example, whenever we generate a new snapshot that can be dow

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #2761

I completely agree. > On Mar 16, 2016, at 10:33 PM, Chris Lattner via swift-dev > wrote: > > IMO, we should remove/disable this test unless it can be “really” fixed. It > is unacceptable to have a test that we know injects noise into our CI > systems. Having to second guess whether failures

[swift-dev] Swift 2.2 released!

Hi everyone, I am very pleased to announce the release of Swift 2.2! This is the first release of Swift since Swift became an open source project. Swift 2.2 began it’s convergence in mid-January when it branched from master, and since then is had taken curated changes (bug fixes and some lang

[swift-dev] Pull requests for Swift 2.2.1

Hi everyone, For those of you creating pull requests for Swift 2.2.1, please do the following: - Add the ‘Swift 2.2.x’ milestone in the pull request. - Assign the pull request to me. - Optionally: Put "[Swift 2.2.1]” in the pull request title. Thanks! Ted___

Re: [swift-dev] Requiring Xcode 7.3 to build Swift master for Apple platforms?

Hi Grant, On OS X generally speaking we plan on staying with the latest released tools. It simplifies the development model and allows the project to take advantage of advances in the toolchain. Unless there is a strong compelling reason, we don't wish to hold Swift development back when ther

Re: [swift-dev] Including `FileCheck` in downloadable toolchains

SGTM > On Apr 21, 2016, at 9:28 PM, Daniel Dunbar via swift-dev > wrote: > > Hi all, > > I would like to propose that we include `FileCheck` in the downloadable > toolchains. > > The downloadable toolchains are quite useful for people who are wanting to > work on Swift projects that use Fil

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - LLDB Incremental - OS X (swift 2.2) #2988

I'll work with John and the LLDB folks to see why his change would break LLDB (or at least the test). > On Apr 23, 2016, at 8:54 AM, no-re...@swift.org wrote: > > [FAILURE] oss-lldb-swift-2.2-incremental-osx [#2988] > > Build URL: > https://ci.swift.org/job/oss-lldb-swift-2.2-incremental-os

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - LLDB Incremental - OS X (swift 2.2) #2988

The failure possibly looks like an environmental issue. We'll see if it reproduces when another integration cycles later today. > On Apr 23, 2016, at 12:14 PM, Ted kremenek wrote: > > I'll work with John and the LLDB folks to see why his change would break LLDB > (or at least the test). > >>

[swift-dev] swift-3.0-branch to be made; details to be announced soon

Hi everyone, We’re going to create a "swift-3.0-branch" branch across the various Swift repositories within the next couple days. The branch will be used to provide a more stable baseline for producing qualified snapshots for Swift 3. With a large number of Swift 3 changes having landed the i

[swift-dev] Everyone with commit access can now initiate CI from pull requests

A change got rollout out to the continuous integration (CI) system last night that enables everyone with commit access (Apple and non-Apple contributors) to initiate CI from pull requests. This has been something we've desired since we rolled out CI-support in Swift pull requests, and I'm thril

[swift-dev] Swift 3.0 release process

Hi everyone, I just posted the branching and release process for Swift 3.0: https://swift.org/blog/swift-3-0-release-process/ Please take a read and let me know if there are any questions. Cheers, Ted

[swift-dev] please assign GitHub milestones for pull requests for swift-3.0-preview-1

Hi everyone, For pull requests to swift-3.9-preview-1, when you create them please also put them on the “Swift 3.0 Preview 1” milestone. If they are on the swift repository, please assign them to me, and for other repositories to the corresponding release manager. Thanks! Ted_

Re: [swift-dev] Swift compiler plugins

Hi Jorge, I think being able to facilitate tooling that integrates more closely with the Swift compiler would possibly be a great addition to the project, if it can be done well. The main concerns I have are stability of the plugin interface and security. For stability of the plugin interfac

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (swift-3.0-preview-1) #59

I think this is because I merged the clang PR without merging the paired swift PR. I’ve merged the latter, so this should hopefully clear up. > On May 23, 2016, at 2:16 PM, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-3.0-preview-1-incremental-RA-linux-ubuntu-15_10 [#

[swift-dev] Swift 3.0 Preview 1 and some important logistics for those working on Swift

Hi everyone, I am happy to announce that Preview 1 of Swift 3.0 has just been posted: https://swift.org/blog/swift-3-0-preview-1-released Downloads for Linux are available on Swift.org, and Preview 1 is included in Xcode 8 beta 1. Importan

[swift-dev] swift-3.0-preview-2-branch has been cut

Hi everyone, The swift-3.0-preview-2-branch has been cut. It will be managed in the same way as swift-3.0-preview-1-branch as described in the Swift 3.0 Release Process blog post. Cheers, Ted ___ swift-dev mailing list swift-dev@swift.org https://lis

Re: [swift-dev] Descriptive Protocol non-conformance errors

> On Jul 6, 2016, at 8:24 PM, Douglas Gregor via swift-dev > wrote: > > >> On Jun 25, 2016, at 1:19 PM, Sean Alling via swift-dev >> wrote: >> >> Hi everyone, >> >> I’m suggesting a change to the compiler that returns an error when an object >> 'does not conform to protocol’ to nest sub-

[swift-dev] Endgame for Swift 3

Hi everyone, Swift 3 has shaped up to be a remarkable release — a product of the inspiration, ideas, and hard labor many people from across the Swift open source community. It is now time, however, to talk about the endgame for the release. Here are the key points: The last day to take planne

Re: [swift-dev] [swift-evolution] Endgame for Swift 3

Good question. Dave/Dmitri: do you have a recommendation here? I can see either the JIRA issues referencing the proposal (if one exists) or updating the gist. I prefer the former. > On Jul 15, 2016, at 11:18 AM, Will Field-Thompson wrote: > > Is there any way to tell which of the changes in

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - OS X (master) #5225

I have temporarily configured the job to always delete the workspace. > On Jul 15, 2016, at 2:07 PM, Andrew Trick via swift-dev > wrote: > > Does anyone have permission to clear this workspace? If I don’t hear back > soon I’ll probably have to make a dummy checkin the overlay… > > -Andy > >>

[swift-dev] End of source-breaking changes for Swift 3

Dear friends, Today is July 27 — and the last planned day to take source-breaking changes for Swift 3. It has been an incredible ride to this point, so let's take stock of where we are. Here are the list of currently accepted — but not yet (fully) implemented — evolution proposals (this is draw

Re: [swift-dev] [swift-evolution] End of source-breaking changes for Swift 3

> On Jul 27, 2016, at 12:50 PM, Chris Lattner wrote: > > > >> On Jul 27, 2016, at 12:45 PM, Slava Pestov via swift-evolution >> mailto:swift-evolut...@swift.org>> wrote: >> >> >>> On Jul 27, 2016, at 12:38 PM, Ted Kremenek vi

Re: [swift-dev] [swift-evolution] End of source-breaking changes for Swift 3

- swift-evolution, swift-evolution-announce Dave/Max: can you speak this? > On Jul 27, 2016, at 3:17 PM, Tony Allevato wrote: > > I noticed that while SE-0091 appears to be implemented (from a cursory glance > at some of the affected types like Equatable and String), it looks like the > name

Re: [swift-dev] clang: warning: argument unused during compilation: '-MMD'

-Wno-unused-variable would drop warnings about variables in *code* that are not used. This is about a driver option that is not being used. We should just not pass that driver option. I don't recall offhand what it does (or intends to). > On Jul 29, 2016, at 11:32 AM, Dave Abrahams via swif

Re: [swift-dev] [swift-corelibs-dev] [swift-build-dev] JIRA workflow: "Resolved" -> "Verify"?

I agree with Jordan. I think we can have a Verify state (per Jordan’s suggestion), and then have a script go over old tickets in Verify for a while and move them to Close. > On Aug 15, 2016, at 10:15 AM, Jordan Rose via swift-corelibs-dev > wrote: > > It hasn’t been used so much so far, but o

Re: [swift-dev] __swift__

> On Aug 25, 2016, at 3:11 PM, Jordan Rose via swift-dev > wrote: > >> >> On Aug 25, 2016, at 14:58, Douglas Gregor > > wrote: >> >>> >>> On Aug 25, 2016, at 2:48 PM, Jordan Rose >> > wrote: >>> On Aug 25, 2016, at 9:38, Dou

Re: [swift-dev] Swift CI: Pull Request Check Status

Awesome! Thanks Mishal! Do we have a persistent place where we are documenting these options? > On Aug 25, 2016, at 1:46 PM, mishal_shah via swift-dev > wrote: > > With new changes to the pull request jobs, if you trigger full test suite it > will also update the smoke test checks. > Trigge

Re: [swift-dev] Swift CI: Pull Request Check Status

ter. >> >> >> Thanks, >> Mishal Shah >> Sent from my iPhone >> >>> On Aug 28, 2016, at 2:04 PM, Michael Gottesman wrote: >>> >>> >>>> On Aug 26, 2016, at 9:50 PM, Ted Kremenek via swift-dev >&

[swift-dev] Swift 3.0 released!

Hi everyone, Swift 3.0 has been officially released: https://swift.org/blog/swift-3-0-released/ This moment marks an incredible achievement for the Swift open source community. The release is the culmination of an incredible amount of discussion and implementation work to bring it all tog

[swift-dev] why are we accepting switch statements with duplicate conditions?

Hi everyone, Joe Shajrawi nominated an optimizer fix for Swift 3.0.1 where the optimizer was crashing due to duplicate conditions in aswitchstatement: https://bugs.swift.org/browse/SR-2512 https://github.com/apple/swift/pull/4747

Re: [swift-dev] [swift-users] Swift 3.0 released!

The Xcode 8.0 that GM'ed on the App Store included Swift 3.0, the same tag we published to GitHub. > On Sep 14, 2016, at 10:28 AM, Patrice Kouame wrote: > > Congrats! Did it make it in Xcode 8 build 8A218a? So many GMs flying around > over the last few days. > >> On Sep 13, 2016, at 10:15 PM

Re: [swift-dev] Swift CI PR builder dispatch linux failure

Dispatch is a separate project. There isn’t a dependency in the Dispatch project to tell it is building with a new compiler. The project would need to be modified to add a dependency on the swiftc binary being used to compile this project. > On Sep 21, 2016, at 9:39 AM, Mishal Shah via swift-

Re: [swift-dev] Swift CI PR builder dispatch linux failure

+ Daniel Daniel: how hard would it be for the Dispatch project to be modified to add the swiftc binary used to build the project as a dependency? > On Sep 23, 2016, at 12:55 PM, Ted Kremenek via swift-dev > wrote: > > Dispatch is a separate project. There isn’t a dependency in

Re: [swift-dev] Swift CI PR builder dispatch linux failure

ing these changes since we still don’t have the whitelist in place for > Apple contributors to do so… > > Daniel > > On Sep 23, 2016, at 13:00, Ted Kremenek wrote: > > + Daniel > > Daniel: how hard would it be for the Dispatch project to be modified to add > t

Re: [swift-dev] Major SwiftPM compile time regression

Does this look related to the type checker (I saw Mark’s comments in the SR) or something else? > On Sep 24, 2016, at 3:23 PM, Daniel Dunbar via swift-dev > wrote: > > Swift TOT is currently taking a very long time (and upwards of 8GB) to build > SwiftPM. I filed: > https://bugs.swift.org/br

Re: [swift-dev] Swift vim support

EADME to the swift/utils/vim directory, explaining its contents > and how to install them. :) > > I feel like this is a happy middle ground to what Ted K. proposed back in > January. Thoughts? > > - Brian Gesiak > > >> On Thu, Jan 7, 2016 at 10:02 PM, Ted kremenek

Re: [swift-dev] Cleaning up stale branches?

> On Oct 21, 2016, at 12:49 PM, John McCall via swift-dev > wrote: > >>> On Oct 21, 2016, at 12:23 PM, Daniel Dunbar wrote: >>> On Oct 21, 2016, at 12:14 PM, Dave Abrahams via swift-dev >>> wrote: >>> >>> >>> on Fri Oct 21 2016, John McCall wrote: >>> > On Oct 21, 2016, at 10:39 AM,

Re: [swift-dev] Cleaning up stale branches?

> On Oct 21, 2016, at 1:54 PM, Dave Abrahams via swift-dev > wrote: > > > on Fri Oct 21 2016, John McCall wrote: > >>> On Oct 21, 2016, at 12:23 PM, Daniel Dunbar wrote: On Oct 21, 2016, at 12:14 PM, Dave Abrahams via swift-dev > > wrote:

[swift-dev] announcing Server APIs work group

Hi everyone, I’d like to announce the introduction of a new Server APIs work group: https://swift.org/blog/server-api-workgroup/ From the blog post: "Since Swift became available on Linux there has been a huge amount of interest in using Swift on the server, resulting in the emergence of a n

[swift-dev] swift-3.0-branch and 3.0.2

Hi everyone, I just bumped the compiler version on swift-3.0-branch to 3.0.2 to allow for another potential dot fix release after 3.0.1. The criteria for taking changes into swift-3.0-branch will be fairly stringent, taking only high value bug fixes with low to moderate risk. Ted _

Re: [swift-dev] PVS-Studio static analysis results for the Swift project

Hi Brian, I know you sent this out 7 days ago, but thanks very much for doing this! Ted > On Nov 7, 2016, at 1:56 PM, Brian Gesiak via swift-dev > wrote: > > Hello all, > > The latest LLVM Weekly > featured a blog post by s

Re: [swift-dev] proposed change for master-next merges

This approach seems good to me. It strikes a good pragmatic balance. > On Dec 7, 2016, at 7:30 PM, Bob Wilson via swift-dev > wrote: > > I would like to make a change in the way we handle the master-next branch. > > Summary: I’d like to switch to a model where we continuously test against the

[swift-dev] Swift 3.1 Release process announced

The release process for Swift 3.1 has now been posted to Swift.org: https://swift.org/blog/swift-3.1-release-process Please take a look at the dates and branch management plans in the post. Also, we are switching to having daily snapshots of the swift-3.1-branch instead of ad hoc "developer

Re: [swift-dev] [swift-lldb-dev] Swift 3.1 Release process announced

Thank you for the correction! > On Dec 9, 2016, at 12:58 PM, Dmitry Shevchenko wrote: > > The correct url is https://swift.org/blog/swift-3-1-release-process/ > , just in case. > > On Fri, Dec 9, 2016 at 3:55 PM Ted Kremenek via swift-lldb-dev

Re: [swift-dev] help diagnosing swiftpm BuildToolTests.testBuildAndClean failure on libdispatch PR testing

[ + Daniel, Rick, concerning SwiftPM piece ] > On Jan 27, 2017, at 10:15 AM, David P Grove via swift-dev > wrote: > > Hi, > > The libdispatch Linux PR testing > (https://ci.swift.org/view/Pull%20Request/job/swift-corelibs-libdispatch-PR-Linux/) > has been failing due to a timeout in the swif

[swift-dev] Swift 4 Release Process announced

Hi everyone, Swift 3.1 is still in convergence (having branched off already from master), but I’ve gone ahead and posted a blog post about the release management process for Swift 4.0: https://swift.org/blog/swift-4-0-release-process/ The

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.10 (master) #2035

I have temporarily configured the job to clean the workspace on build, and kicked off another build. > On Feb 20, 2017, at 9:30 PM, Slava Pestov via swift-dev > wrote: > > This needs someone to clean the workspace. > >> On Feb 20, 2017, at 9:30 PM, no-re...@swift.org

[swift-dev] ABI dashboard now up

Hi everyone, We now have a dashboard up on Swift.org to track remaining tasks for ABI stability: https://swift.org/abi-stability/ The contents of the dashboard (which we may refine over time*) are largely drawn from JIRA and the ABI manifesto: https://github.com/apple/swift/blob/master/do

[swift-dev] final re-branching for Swift 4 is June 1

We’ve been periodically branching swift-4.0-branch from master, per: https://swift.org/blog/swift-4-0-release-process/ The last re-branching from master to swift-4.0-branch will be June 1. Changes will continue to be pulled into Swift 4 afte

[swift-dev] help with implementing SE-0155 and SE-0169

The following two unimplemented SE proposals are fairly impactful on Swift’s core programming model: SE-0155 Normalize Enum Case Representation SE-0169 Improve Interaction Between private Declarations and Extensions Both proposals were only recently accepted, but would be good to get in for Sw

Re: [swift-dev] swift-format editor integration

Hi Saleem, My apologies for the delay. Generally speaking, doesn't feel to me that these kinds of enhancements should be going into the 'swift' repository. We have some basic support files for editors in the repository, but largely those are there for historical reasons (largely convenience w

[swift-dev] version bump to 4.0 may require clean rebuild

I bumped the version of the compiler to 4.0. This was a change in a variety of places, including CMakeLists.txt. If you encounter an assertion failure when building Version.cpp likely you need to clean rebuild ‘swift’.___ swift-dev mailing list swift-

Re: [swift-dev] swift-format editor integration

> On Apr 28, 2017, at 8:17 AM, Saleem Abdulrasool wrote: > > Hi Ted, > > I think that what I'm proposing adding is quite small. It has a mirror > equivalent in the clang repository. I thought about it more, and you convinced me. I’m fine with taking it. Can you revise the description in PR

[swift-dev] final swift-4.0-branch created for 'swift' repository

This afternoon we did the final re-branch of swift-4.0-branch from master for the ‘swift’ repository. All further changes for the Swift 4 release that will change either the compiler or Standard Library need to be made as pull requests against this branch. The following repositories have not d

[swift-dev] open sourcing refactoring and other goodies announced at WWDC

Hi everyone, This afternoon at WWDC we announced a new refactoring feature in Xcode 9 that supports Swift, C, Objective-C, and C++. We also announced we will be open sourcing the key parts of the engine that support file-level transformations, as well as the compiler pieces for the new index-w

[swift-dev] Swift 4.0 released!

I am pleased to announce that Swift 4.0 has been officially released: https://swift.org/blog/swift-4-0-released/ Swift 4 is available in Xcode 9 (which went live on the Mac App Store earlier today) and we will be posting an official toolchain shortly as well (likely early tomorrow morning).

[swift-dev] Swift 4.1 release process

Hi everyone, I just posted the branch management details for Swift 4.1: https://swift.org/blog/swift-4-1-release-process/ This is a release freshly branched from master. The details are in the blog post, but the key point is that we will c

Re: [swift-dev] "Near-miss" warnings for protocol conformances

> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev > wrote: > > Unlabeled single-value initializers are probably going to cause a number of > false positives, because we can’t figure out which one we meant. Hi Doug, This all looks very promising. Do you have any thoughts about how

Re: [swift-dev] "Near-miss" warnings for protocol conformances

> On Oct 31, 2017, at 11:09 PM, Douglas Gregor wrote: > > > >> On Oct 31, 2017, at 11:08 PM, Ted Kremenek wrote: >> >> >> >>> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev >>> wrote: >>> >>> Unlabeled single-value initializers are probably going to cause a number of >>> fa

Re: [swift-dev] deprecating -Ounchecked

On Nov 10, 2017, at 8:43 PM, Chris Lattner via swift-dev wrote: >> On Nov 4, 2017, at 9:52 PM, Erik Eckstein wrote: Are compiler flags within the scope of the evolution process? -Osize has no effect on source compatibility or any other user-visible aspect of the language itse

Re: [swift-dev] Highlighting other platforms for Swift?

Hi Ron, This is a great question. We’re actively setting up support to wire in up externally hosted CI bots to our CI infrastructure so that the community can help support the bringup and testing of Swift on other platforms beyond the officially supported platforms. The tentative rollout for

[swift-dev] Final re-branch for Swift 4.1 pushed out to December 4

FYI: The final re-branch of swift-4.1-branch from master will be pushed out a week to December 4. There’s a variety of things in flight right now that I expect to land this week, and overall it looks like a better plan to just push the branch out one week. _

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

Daniel, When you changed llbuild to require C++14, what platforms did you take into account with that change? If you have already done the assessment here it could speed a resolution of a decision. Thanks, Ted > On Dec 13, 2017, at 3:19 PM, Daniel Dunbar via swift-lldb-dev > wrote: > > FWI

Re: [swift-dev] Conditional conformance: Removing the opt-in flag

On Dec 18, 2017, 4:53 PM -0800, Douglas Gregor via swift-dev , wrote: > Hi all, > > A little while back, I added an error to the Swift 4.1 compiler that > complains if one tries to use conditional conformances, along with a flag > “-enable-experimental-conditional-conformances” to enable the fe

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

Fair enough. We care about swiftc and llbuild building a variety of platforms today — FreeBSD, Rasberry Pi, etc.  My impression is that C++14 is generally supported by both (a) the mininum versions of the distributions we support today and (b) the current versions of the platforms we’d like to

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

> On Dec 19, 2017, at 2:31 PM, Daniel Dunbar wrote: > > > >> On Dec 19, 2017, at 2:27 PM, Ted Kremenek > > wrote: >> >> Fair enough. >> >> We care about swiftc and llbuild building a variety of platforms today — >> FreeBSD, Rasberry Pi, etc. My impression is tha

Re: [swift-dev] Conditional conformance: Removing the opt-in flag

> On Dec 19, 2017, at 3:59 PM, Douglas Gregor wrote: > > > >> On Dec 19, 2017, at 2:26 PM, Ted Kremenek via swift-dev >> wrote: >> >> >>> On Dec 18, 2017, 4:53 PM -0800, Douglas Gregor via swift-dev >>> , wrote: >>> Hi all,

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

> On Dec 19, 2017, at 5:08 PM, Saleem Abdulrasool wrote: > > > >>> On Dec 19, 2017, at 3:59 PM, Ted Kremenek wrote: >>> >>> >>> On Dec 19, 2017, at 2:31 PM, Daniel Dunbar wrote: On Dec 19, 2017, at 2:27 PM, Ted Kremenek wrote: Fair enough. >>

Re: [swift-dev] Conditional conformance: Removing the opt-in flag

> On Dec 19, 2017, at 8:57 PM, Douglas Gregor wrote: > > > > Sent from my iPhone > >> On Dec 19, 2017, at 8:31 PM, Ted Kremenek wrote: >> >> >> >>> On Dec 19, 2017, at 3:59 PM, Douglas Gregor wrote: >>> >>&g

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

On Dec 19, 2017, 8:33 PM -0800, Ted Kremenek via swift-dev , wrote: > > > On Dec 19, 2017, at 5:08 PM, Saleem Abdulrasool wrote: > > > > > > > > On Dec 19, 2017, at 3:59 PM, Ted Kremenek wrote: > > > > > > > > > > &

Re: [swift-dev] Conditional conformance: Removing the opt-in flag

> On Dec 19, 2017, at 9:39 PM, Ted Kremenek via swift-dev > wrote: > > > > On Dec 19, 2017, at 8:57 PM, Douglas Gregor <mailto:dgre...@apple.com>> wrote: > >> >> >> Sent from my iPhone >> >> On Dec 19, 2017, a

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

I’m pinging some folks, but not everybody is back yet. I hope to resolve this ASAP. > On Jan 2, 2018, at 11:33 AM, Saleem Abdulrasool wrote: > >> On Wed, Dec 20, 2017 at 4:26 PM, Ted Kremenek wrote: >> >>> On Dec 19, 2017, 8:33 PM -0800, Ted Kremenek

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

t; Jim > > > >> On Jan 3, 2018, at 8:46 PM, Ted Kremenek via swift-lldb-dev >> wrote: >> >> I’m pinging some folks, but not everybody is back yet. I hope to resolve >> this ASAP. >> >> On Jan 2, 2018, at 11:33 AM, Saleem Abdulrasool >> w

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

kewise impractical for us to support both Ubuntu 14.04 > (pre-c++14 libstdc++) and Windows (needs c++14, IIUC). > > Caveat: I am not an expert on either distributing software on Linux or > Windows, I'm just making the bots happy. > > Ben > >> On Jan 5, 2018, at