Title: Report
[FAILURE] oss-swift-package-osx [#482]
Build URL:https://ci.swift.org/job/oss-swift-package-osx/482/
Project:oss-swift-package-osx
Date of build:Thu, 12 Oct 2017 20:14:50 -0500
Build duration:55 min
Identified problems:Compile Error: This build failed becaus
The nice thing about this setup is that it degrades nicely for the 1000-case
enum. You have a static check in the compiler for if theNumberOfKnownEnumCases
>= SOME_REASONABLE_MAX (or — in the future — as complicated a decision as you
want given the number of total cases and the number of cases y
Hi Jordan,
Bertrand (ex-Apple) would sometimes say during API design that “easy things
things should be easy, and hard things should be possible”.
I don’t think you guys need to go out of your way to make the autogenerated
1000-case enum scenario “easy". If people are clever enough to do that,
Our worry when discussing it was that someone might have an autogenerated
1000-case enum, and passing an entire page worth of resolved symbols might not
be worth it.
(It is of course questionable for someone to have an autogenerated 1000-case
enum as part of their binary interface, and then for
Title: Report
[FAILURE] oss-swift-4.0-package-osx [#438]
Build URL:https://ci.swift.org/job/oss-swift-4.0-package-osx/438/
Project:oss-swift-4.0-package-osx
Date of build:Thu, 12 Oct 2017 14:09:41 -0500
Build duration:3 hr 25 min
Changes
No Chang
I like Joe’s idea here, with the extension that the client should have just one
of these arrays that contains all the symbols that it knows about at the time
it was compiled:
I.e. in the client:
static myKnownOpaqueEnumCases = [MyOpaqueEnum.intCase, MyOpaqueEnum.middleCase,
MyOpaqueEnum.string
So, an update! This came up while I was talking to members of the core team,
and ChrisL felt very strongly that restricting reordering of enum elements was
a no-go, since it would be the only part of the language that worked this way
(even if it only mattered for binary frameworks). Ted also rig
Now I am finally able to build the Swift runtime with an extended object
header and run some benchmarks. For future reference, in addition to
making changes similar to the commits which Greg pointed to, I needed to
change the Foundation library's CFRuntimeBase class which mirrors the
Swift's objec
Hi Alex,
Tested the master branch, which has the same behavior as V4.0 branch.
Just wonder how to debug the compiler swift code if the debugger is not
able to show the values.
Thanks,
Sam Ding,
Linux on z Systems Open Source Ecosystem
IBM Toronto Lab,
email: samd...@ca.ibm.com
phone: (905)413
Title: Report
[FAILURE] oss-swift-package-osx [#477]
Build URL:https://ci.swift.org/job/oss-swift-package-osx/477/
Project:oss-swift-package-osx
Date of build:Thu, 12 Oct 2017 02:58:17 -0500
Build duration:2 hr 13 min
Identified problems:Regression test failed: This build
10 matches
Mail list logo
