[swift-dev] [SourceKit] static modifier

[Jose Cheyo Jimenez via swift-dev]

Hi, 
I am trying to understand why sourceKit is reporting `static` as a 
"source.lang.swift.syntaxtype.keyword" instead of a 
“source.lang.swift.syntaxtype.attribute.builtin”?

All the modifiers in this list (except for class and static) are `builtin` 
https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/Declarations.html#//apple_ref/swift/grammar/declaration-modifiers
 


I am trying to build a linting rule to enforce a consistent order of these 
attributes.  https://github.com/realm/SwiftLint/issues/387 


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

[swift-dev] Porting Swift to Haiku

[Joseph Calvin Hill via swift-dev]

Hello swift-dev!

I'm one of the selected GSoC 2017 students under the Haiku Project [0] and I 
intend to add Haiku support to the Swift compiler and its standard libraries. 
[1]  Haiku is an open-source operating system that specifically targets 
personal computing and aims to be a platform that is easy to use and learn for 
both end-users and developers, whilst retaining BeOS ABI compatibility [2]. My 
plan is to only support 64 bit Haiku (x86_64-unknown-haiku) for now, 32 bit 
support is also a possibility but I’m not sure if this will get in the way of 
Swift’s goals? (IIRC there was a 32 bit Linux port that hasn’t been merged 
upstream.)

I have already patched the build-script and some other CMakeFiles for initial 
support in my swift fork, but they are based on the ’swift-3.1-branch' sources 
[3]. As I plan to cleanup these changes and merge them upstream, should I be 
targeting my porting efforts to Swift 4 rather than Swift 3.1.1? My final 
proposal [4] documents the project timeline for executing this porting task.

Thanks,
Joseph Hill

[0] https://www.haiku-os.org
[1] https://summerofcode.withgoogle.com/projects/#5744000681115648
[2] https://www.haiku-os.org/about
[3] 
https://github.com/return/swift/commit/c8253ab3afa238c16ca9389d169c0659dc10b520.diff
[4] https://www.dropbox.com/s/hp9z4azdem6gume/Final_Proposal.pdf?dl=0
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Porting Swift to Haiku

[William Dillon via swift-dev]

Hi Joseph,

That’s awesome!!  I love BeOS back in the day.

I work on the 32-bit swift port for ARM/Linux.  Swift works just fine with 
32-bit systems.

Good luck!

- Will


On May 7, 2017 at 2:19:15 PM, Joseph Calvin Hill via swift-dev 
(swift-dev@swift.org) wrote:

Hello swift-dev!

I'm one of the selected GSoC 2017 students under the Haiku Project [0] and I 
intend to add Haiku support to the Swift compiler and its standard libraries. 
[1]  Haiku is an open-source operating system that specifically targets 
personal computing and aims to be a platform that is easy to use and learn for 
both end-users and developers, whilst retaining BeOS ABI compatibility [2]. My 
plan is to only support 64 bit Haiku (x86_64-unknown-haiku) for now, 32 bit 
support is also a possibility but I’m not sure if this will get in the way of 
Swift’s goals? (IIRC there was a 32 bit Linux port that hasn’t been merged 
upstream.)

I have already patched the build-script and some other CMakeFiles for initial 
support in my swift fork, but they are based on the ’swift-3.1-branch' sources 
[3]. As I plan to cleanup these changes and merge them upstream, should I be 
targeting my porting efforts to Swift 4 rather than Swift 3.1.1? My final 
proposal [4] documents the project timeline for executing this porting task.

Thanks,
Joseph Hill

[0] https://www.haiku-os.org
[1] https://summerofcode.withgoogle.com/projects/#5744000681115648
[2] https://www.haiku-os.org/about
[3] 
https://github.com/return/swift/commit/c8253ab3afa238c16ca9389d169c0659dc10b520.diff
[4] https://www.dropbox.com/s/hp9z4azdem6gume/Final_Proposal.pdf?dl=0
___
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] swift.org nightlies are old

[Karl Wagner via swift-dev]

It looks like the nightlies on swift.org haven’t been uploading properly for 
some time now. The latest toolchain from master is dated April 26th.

Could somebody look in to it?

Thanks

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

Re: [swift-dev] swift.org nightlies are old

[Bob Wilson via swift-dev]

There was a problem with some test failures blocking the build. We should at 
least be able to xfail those tests to get things unblocked tomorrow.

> On May 7, 2017, at 8:49 PM, Karl Wagner via swift-dev  
> wrote:
> 
> It looks like the nightlies on swift.org haven’t been uploading properly for 
> some time now. The latest toolchain from master is dated April 26th.
> 
> Could somebody look in to it?
> 
> Thanks
> 
> - Karl
> ___
> 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