> On Sep 29, 2017, at 18:21, Jordan Rose via swift-dev
> wrote:
>
> Hello again, swift-dev! This is a sort of follow-up to "What can you change
> in a fixed-contents struct" from a few weeks ago, but this time concerning
> enums. Worryingly, this seems to be an important consideration even fo
I think that you are going to be better served by making things more explicit
for non-exhaustive enums with binary compatibility concerns. I don’t think that
there is a solution that salvages an ordering for a jump table while still
allowing open enums to change during the same @availability ver
I'm looking for all code that uses the is-Swift bit in class metadata.
Uses that I know of:
* Compiler-generated class metadata (addClassDataPointer() in GenMeta.cpp)
* Runtime metadata checks (isTypeMetadata() inMetadata.h)
* Stuff in lldb and other debugging tools
* Stuff in the Objective-C runt
Hello again, swift-dev! This is a sort of follow-up to "What can you change in
a fixed-contents struct" from a few weeks ago, but this time concerning enums.
Worryingly, this seems to be an important consideration even for non-exhaustive
enums, which are normally the ones where we'd want to allo
> On Sep 29, 2017, at 8:08 AM, Sam Ding wrote:
>
> Hi Slava & Joe,
>
> Thank you for the response.
>
> The failed test case is "generic instantiation" of KeyPath.swift. Here is
> details of log:
>
> [ RUN ] key paths.key path generic instantiation
> stdout>>> check failed at /home/wk/sw4/sw
Hi Slava & Joe,
Thank you for the response.
The failed test case is "generic instantiation" of KeyPath.swift. Here is
details of log:
[ RUN ] key paths.key path generic instantiation
stdout>>> check failed
at /home/wk/sw4/swift/test/stdlib/KeyPath.swift, line 193
std
Title: Report
[FAILURE] oss-swift_tools-RA_stdlib-RDA_test-macos-resilience [#58]
Build URL:https://ci.swift.org/job/oss-swift_tools-RA_stdlib-RDA_test-macos-resilience/58/
Project:oss-swift_tools-RA_stdlib-RDA_test-macos-resilience
Date of build:Fri, 29 Sep 2017 03:47:00 -05
