Re: [swift-users] Bls: Re: Swift to Javascript

If you want something supported by Apple, the procedure is to propose it on the swift-evolution list. However, Swift has a very specific set of development priorities right now, so they are almost certainly not going to accept any new proposals for compiler backends or transpilation support for

[swift-users] Bls: Re: Swift to Javascript

I know there are some JS compilers, but I prefer something that is officially supported by Apple. –Mr Bee Pada Rab, 22 Jun 2016 pada 12:45, Austin Zheng menulis: The great thing about Swift being open-source is that anyone can help make it a better language! Here's a good starting poin

Re: [swift-users] Swift to Javascript

The great thing about Swift being open-source is that anyone can help make it a better language! Here's a good starting point: https://kripken.github.io/emscripten-site/index.html Best, Austin > On Jun 21, 2016, at 9:44 PM, Mr Bee via swi

[swift-users] Swift to Javascript

Hi all,  I wish I will be able write web app using Swift instead of JavaScript. It would be wonderfull if we could develop desktop app, mobile app, server-side app, and  web app, all using Swift. It will be complete. Is it possible that someday in the future we would be able to compile Swift code

Re: [swift-users] Swift 3 preview 1 in Xcode 8 and Lowercase enum cases

e ​num should be case-sensitive. If you find it otherwise, you should file a bug. Zhaoxin On Wed, Jun 22, 2016 at 5:48 AM, Stéphane Lizeray wrote: > Hello, > > The following enum > > enum X { > > case A_B > > > } > > is translated to: > > enum X { > > case a_b > > > } > > which is fine. > > But

[swift-users] Swift 3 preview 1 in Xcode 8 and Lowercase enum cases

Hello, The following enum enum X { case A_B } is translated to: enum X { case a_b } which is fine. But: enum X { case AXX_BYY } is migrated to: enum X { case axx_BYY } Shouldn’t it be rather: enum X { case

Re: [swift-users] New Swift Snapshots Available!

Ah, this issue. A workaround is to set your deployment target to iOS 9. We should have it fixed soon. Jordan > On Jun 21, 2016, at 10:46, Charles Lane via swift-users > wrote: > > This is a little snippet of the error : > > :0: error: invalid version number in '-miphoneos-version-min=10.0.0'

Re: [swift-users] New Swift Snapshots Available!

Thanks! I was kind of waiting to see if it was just something dumb that I was doing or didn’t do. But apparently you’ve seen it too. Makes me feel better :-) > Thanks Charles! I have created Jira issue to track this bug. > > https://bugs.swift.org/browse/SR-1853 > > Mishal Shah __

Re: [swift-users] New Swift Snapshots Available!

Thanks Charles! I have created Jira issue to track this bug. https://bugs.swift.org/browse/SR-1853 Mishal Shah > On Jun 21, 2016, at 10:46 AM, Charles Lane via swift-users > wrote: > > This is a little snippet of the error : > > :0: error: invalid version number in '-miphoneos-version-min=10

Re: [swift-users] New Swift Snapshots Available!

This is a little snippet of the error : :0: error: invalid version number in '-miphoneos-version-min=10.0.0' Assertion failed: (Maj < 10 && Min < 100 && Rev < 100 && "Invalid version!"), function getDarwinDefines, file /Users/buildnode/jenkins/workspace/oss-swift-package-osx/llvm/tools/clang/lib

Re: [swift-users] New Swift Snapshots Available!

This is with Xcode 8 beta and the June 20 Development snapshot of swift 3.0. It works fine with the default 3.0 toolchain. > Are you using Xcode 7.3? The new toolchains only support Xcode 8 (because of > SDK requirements and issues with Xcode 7's Clang). > > Jordan > > > > On Jun 21, 2016, a

Re: [swift-users] New Swift Snapshots Available!

I simply created a new single-view project targeting ios 10. I got the error immediately. > Can you reduce the problem to a small test case? Please file a bug report > onbugs.swift.org(http://bugs.swift.org)for this, and include information on > the last toolchain which worked. > > - Daniel >

Re: [swift-users] New Swift Snapshots Available!

Are you using Xcode 7.3? The new toolchains only support Xcode 8 (because of SDK requirements and issues with Xcode 7's Clang). Jordan > On Jun 21, 2016, at 10:17, Daniel Dunbar via swift-users > wrote: > > Can you reduce the problem to a small test case? Please file a bug report on > bugs.

Re: [swift-users] New Swift Snapshots Available!

Can you reduce the problem to a small test case? Please file a bug report on bugs.swift.org for this, and include information on the last toolchain which worked. - Daniel > On Jun 21, 2016, at 5:16 AM, Charles Lane via swift-users > wrote: > > I’m running macOS Sier

[swift-users] Swift 3 preview 1 in xcode 8 and copyBytes

Hello, I am porting a code from swift 1.2 to 3.0 and fails to transform getBytes to copyBytes ? Is the new snapshots resolve this ? And the question I have, because it is not the first issues I got : difference between the 3.0 doc and the compiling error, do I miss something when tuning Xcod

[swift-users] New Swift Snapshots Available!

I’m running macOS Sierra. When I set ios 10 as the deployment target, I get an error: Command failed due to signal: Illegal instruction: 4 It seems to build ok when using 9.3 or below as the build target. ___ swift-users mailing list swift-users@swift.o