Re: [swift-dev] Fixing some build issues on master-next

[Vedant Kumar via swift-dev]

All done :).

8dd7d14 [stable-merge] [swift-llvm-opt] Pass RelocModel as an Optional
06756d2 [stable-merge] [IRGen] Fix what appears to be a typo
2111897 [stable-merge] [driver] Adopt new Error/Expected API
1409a44 [stable-merge] Adopt new setUnnamedAddr API
4a7ba9c [stable-merge] [IRGen] Adopt new coverage encoding API

vedant

> On Jun 27, 2016, at 10:17 AM, Vedant Kumar via swift-dev 
>  wrote:
> 
> Hi all,
> 
> Just as a heads-up, I've got most of the build errors on master-next sorted 
> out locally.
> 
> If you need to push something to the branch, please wait a bit so we don't 
> end up duplicating work. I'll ping this thread when the branch is ready.
> 
> thanks,
> vedant
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] Fixing some build issues on master-next

[Vedant Kumar via swift-dev]

Hi all,

Just as a heads-up, I've got most of the build errors on master-next sorted out 
locally.

If you need to push something to the branch, please wait a bit so we don't end 
up duplicating work. I'll ping this thread when the branch is ready.

thanks,
vedant
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] TWISt-shout Newsletter 2016-06-27

[Kenny Leung via swift-dev]

Here is your TWISt-shout Newsletter for the week of 2016-06-20 to 2016-06-26

https://github.com/pepperdog/TWISt-shout/blob/master/2016/TWISt-shout-2016-06-27.md

Enjoy!

-Kenny



___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [swift-lldb-dev] Proposal for Swift and Ubuntu releases

[Brian Gesiak via swift-dev]

Todd,

Excellent, thanks! Six months seems like plenty of time for me to fix
https://bugs.swift.org/browse/SR-1321. :)

I'll be looking forward to seeing the migrations, good luck!

- Brian Gesiak


On Thu, Jun 23, 2016 at 11:14 PM, Todd Fiala  wrote:

> Update:
>
> I’m now able to successfully run the packaging CI steps on a local Ubuntu
> 16.04 x86_64 setup, passing all the same tests that run on the official
> packaging CI bots.  I think we’re literally down to just needing to get the
> machines procured, configured and put into the Swift CI pool.
>
> -Todd
>
> On Jun 22, 2016, at 1:07 PM, Todd Fiala  wrote:
>
>
> On Jun 22, 2016, at 12:49 PM, Brian Gesiak via swift-lldb-dev <
> swift-lldb-...@swift.org> wrote:
>
> Thanks for raising this discussion, Todd!
>
>
> Hi Brian,
>
> You must be on my brain wave-length.  Now that WWDC is behind us, I just
> raised the Ubuntu 16.04 migration process early this morning.  Expect to
> hear more about this soon once we work out some logistics.
>
> Any input from the core team here? The Swift Android build doesn't
> currently work for Ubuntu 14; see https://bugs.swift.org/browse/SR-1321.
> I'd like to know whether I should prioritize fixing this, or whether I
> should focus on getting the build ready for Ubuntu 16.
>
> - Brian Gesiak
>
>
> Well, getting it working for Ubuntu 14.04 is probably still worth it since
> we are currently supporting it, and plan to support it until we swap it out
> for Ubuntu 16.10 sometime after the October Ubuntu release.  There is
> probably a good 5 - 6 months of coverage left on Swift Ubuntu 14.04 CI.
>
> Does that help?
>
> -Todd
>
>
> On Tue, Apr 26, 2016 at 10:57 AM, Todd Fiala via swift-dev <
> swift-dev@swift.org> wrote:
>
>> Thanks, Ryan.  Yes, the intent was to harmonize with the Ubuntu release
>> philosophy.
>>
>> I haven’t heard any opposition to this plan.  I’m going to move forward
>> with resourcing and executing on this plan.  More communication to follow
>> once those details are worked out.
>>
>> Thanks, all!
>>
>> Sincerely,
>> Todd Fiala
>>
>> On Apr 26, 2016, at 6:24 AM, Ryan Lovelett via swift-lldb-dev <
>> swift-lldb-...@swift.org> wrote:
>>
>> On Thu, Apr 21, 2016, at 01:12 PM, Todd Fiala via swift-lldb-dev wrote:
>>
>> Hi all,
>>
>> I wanted to propose how we can go about handling newer Ubuntu releases in
>> a systematic way.  This covers how we handle Ubuntu on our CI, but also
>> reflects where we'll be focusing effort at any given point.  The primary
>> intent is to support the most recent Ubuntu Long Term Service release and
>> the absolute latest Ubuntu release, with a bit of overlap when phasing out
>> the LTS release that is going out of scope.
>>
>> Since the next release, fast moving or not, is the next Long Term
>> Stability release, Ubuntu 16.04 LTS (available now), I propose we:
>>
>> * swap out our 15.10 fast moving release with Ubuntu 16.04 LTS.
>>
>> * allow 16.04 and 14.04 to co-exist to give our stability-minded
>> community time to switch over to 16.04.
>>
>> When 16.10 comes out in October 2016, we drop 14.04 and move 16.10 onto
>> those builders.
>>
>> This continues to have us testing against the latest release, which will
>> be Ubuntu 16.04 LTS when we switch, gives us the latest stable coverage
>> (also 16.04), and gives our community a little more time with active
>> coverage on 14.04, the previous long term support version.  We’ll then get
>> back to the normal program in October 2016 when we pick up the latest
>> fast-moving release, with coverage on Ubuntu 16.10 and Ubuntu 16.04 LTS.
>>
>> This assumes we want to keep our eyes on no more than two Ubuntu releases
>> at a time, which matches current CI infrastructure planning.
>>
>> Looking forward over the next two years, this is the schedule I’m
>> proposing:
>>
>>
>>
>>- April 2016: Replace Ubuntu 15.10 with Ubuntu 16.04  (coverage:
>>Ubuntu 14.04, Ubuntu 16.04 LTS)
>>- October 2016: Replace Ubuntu 14.04 with Ubuntu 16.10 (coverage:
>>Ubuntu 16.04 LTS, Ubuntu 16.10)
>>- April 2017: Replace Ubuntu 16.10 with Ubuntu 17.04 (coverage:
>>Ubuntu 16.04 LTS, Ubuntu 17.04)
>>- October 2017: Replace Ubuntu 17.04 with Ubuntu 17.10 (coverage:
>>Ubuntu 16.04 LTS, Ubuntu 17.10)
>>- April 2018: Replace Ubuntu 17.10 with Ubuntu 18.04 LTS (coverage:
>>Ubuntu 16.04, Ubuntu 18.04 LTS)
>>
>>
>> Thoughts?  Once we finalize the plan, I'll coordinate with the
>> infrastructure teams and round up resources needed to get Ubuntu 16.04
>> supported and on the CI.
>>
>>
>> This seems to mostly match up with the guidance provided by Canonical and
>> the community around Ubuntu. Therefore it seems reasonable to me.
>>
>> I like it. Consider this a vote in favor.
>>
>>
>> Thanks!
>> Sincerely,
>> Todd Fiala
>> *___*
>> swift-lldb-dev mailing list
>> swift-lldb-...@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-lldb-dev
>>
>>
>> 

[swift-corelibs-dev] Query on NSLog

[Sai Kanduri via swift-corelibs-dev]

Hi All,
 
Currently NSLog  has only one internal function  NSLog()  which can be used only by Foundation classes.Can this be made available as a public API ?
 
 
Thanks & Regards,
 
Sai Hema,Java L3 Support

___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

[swift-corelibs-dev] Implementing(overriding) the "description" property

[Pushkar N Kulkarni via swift-corelibs-dev]

Hello,While working with HTTPCookie I realised that the "description" property isn't currently overridden. This is true for many other Foundation classes subclassing NSObject. Is there any guidance around when this property should be overridden (and when not)? Or is it open for implementation/overriding for all the classes subclassing NSObject? Thank you.Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra


___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Re: [swift-dev] swift --version output changed

[rintaro ishizaki via swift-dev]

I submitted a PR for fixing this.
https://github.com/apple/swift/pull/3222

2016-06-26 7:42 GMT+09:00 Dmitri Gribenko via swift-dev :

> + Michael, who has been working on CMake changes.
>
> On Sat, Jun 25, 2016 at 2:48 PM, Joseph Bell via swift-dev
>  wrote:
> > Howdy,
> >
> > I noticed in a build today that the output of swift --version has
> changed.
> > Today's build:
> >
> > swift --version
> > Swift version 3.0-dev
> > Target: x86_64-unknown-linux-gnu
> >
> > Earlier this week:
> > swift --version
> > Swift version 3.0-dev (LLVM fc970689d4, Clang 460d629e85, Swift
> 1f2b5ee7fb)
> > Target: x86_64-unknown-linux-gnu
> >
> > If this change wasn't inadvertent what was the rationale?  Having the
> hash
> > tags of LLVM, Clang, and Swift are quite useful here.
> >
> > Joe
> >
> > --
> > Joseph Bell
> > http://dev.iachieved.it/iachievedit/
> > @iachievedit
> >
> > ___
> > swift-dev mailing list
> > swift-dev@swift.org
> > https://lists.swift.org/mailman/listinfo/swift-dev
> >
>
>
>
> --
> main(i,j){for(i=2;;i++){for(j=2;j (j){printf("%d\n",i);}}} /*Dmitri Gribenko */
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev