<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 30. Sep 2017, at 20:23, Xiaodi Wu via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Sat, Sep 30, 2017 at 11:58 AM, <span dir="ltr" class=""><<a href="mailto:swift-dev-request@swift.org" target="_blank" class="">swift-dev-request@swift.org</a>></span> wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Message: 2<br class="">
Date: Fri, 29 Sep 2017 18:21:44 -0700<br class="">
From: Jordan Rose <<a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a>><br class="">
To: swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>><br class="">
Subject: [swift-dev] What can you change in a non-exhaustive enum?<br class="">
Message-ID: <<a href="mailto:31DF689E-1AD3-47CB-9FCE-6CBC7E34BC43@apple.com" class="">31DF689E-1AD3-47CB-9FCE-<wbr class="">6CBC7E34BC43@apple.com</a>><br class="">
Content-Type: text/plain; charset="utf-8"<br class="">
<br class="">
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 allow a developer to do anything and everything that doesn't break source compatibility.<br class="">
<br class="">
[This only affects libraries with binary compatibility concerns. Libraries distributed with an app can always allow the app to access the enum's representation directly. That makes this an Apple-centric problem in the near term.]<br class="">
<br class="">
So, what's the issue? We want to make it efficient to switch over a non-exhaustive enum, even from a client library that doesn't have access to the enum's guts. We do this by asking for the enum's tag separately from its payload (pseudocode):<br class="">
<br class="">
switch getMyOpaqueEnumTag(&<wbr class="">myOpaqueEnum) {<br class="">
case 0:<br class="">
var payload: Int<br class="">
getMyOpaqueEnumPayload(&<wbr class="">myOpaqueEnum, 0, &payload)<br class="">
doSomething(payload)<br class="">
case 1:<br class="">
var payload: String<br class="">
getMyOpaqueEnumPayload(&<wbr class="">myOpaqueEnum, 1, &payload)<br class="">
doSomethingElse(payload)<br class="">
default:<br class="">
print("unknown case")<br class="">
}<br class="">
<br class="">
The tricky part is those constant values "0" and "1". We'd really like them to be constants so that the calling code can actually emit a jump table rather than a series of chained conditionals, but that means case tags are part of the ABI, even for non-exhaustive enums.<br class="">
<br class="">
Like with struct layout, this means we need a stable ordering for cases. Since non-exhaustive enums can have new cases added at any time, we can't do a simple alphabetical sort, nor can we do some kind of ordering on the payload types. The naive answer, then, is that enum cases cannot be reordered, even in non-exhaustive enums. This isn't great, because people like being able to move deprecated enum cases to the end of the list, where they're out of the way, but it's at least explainable, and consistent with the idea of enums some day having a 'cases' property that includes all cases.<br class="">
<br class="">
Slava and I aren't happy with this, but we haven't thought of another solution yet. The rest of this email will describe our previous idea, which has a fatal flaw.<br class="">
<br class="">
<br class="">
Availability Ordering<br class="">
<br class="">
In a library with binary compatibility concerns, any new API that gets added should always be explicitly annotated with an availability attribute. Today that looks like this:<br class="">
<br class="">
@available(macOS 10.13, iOS 11, tvOS 11, watchOS 4, *)<br class="">
<br class="">
It's a model we only support for Apple platforms, but in theory it's extendable to arbitrary "deployments". You ought to be able to say `@available(MagicKit 5)` and have the compiler actually check that.<br class="">
<br class="">
Let's say we had this model, and we were using it like this:<br class="">
<br class="">
public enum SpellKind {<br class="">
case hex<br class="">
case charm<br class="">
case curse<br class="">
@available(MagicKit 5)<br class="">
case blight<br class="">
@available(MagicKit 5.1)<br class="">
case jinx<br class="">
}<br class="">
<br class="">
"Availability ordering" says that we can derive a canonical ordering from the names of cases (which are API) combined with their versions. Since we "know" that newly-added cases will always have a newer version than existing cases, we can just put the older cases first. In this case, that would give us a canonical ordering of [charm, curse, hex, blight, jinx].<br class="">
<br class="">
<br class="">
The Fatal Flaw<br class="">
<br class="">
It's time for MagicKit 6 to come out, and we're going to add a new SpellKind:<br class="">
<br class="">
@available(MagicKit 6)<br class="">
case summoning<br class="">
// [charm, curse, hex, blight, jinx, summoning]<br class="">
<br class="">
We ship out a beta to our biggest clients, but realize we forgot a vital feature. Beta 2 comes with another new SpellKind:<br class="">
<br class="">
@available(MagicKit 6)<br class="">
case banishing<br class="">
// [charm, curse, hex, blight, jinx, banishing, summoning]<br class="">
<br class="">
And now we're in trouble: anything built against the first beta expects 'summoning' to have tag 5, not 6. Our clients have to recompile everything before they can even try out the new version of the library.<br class="">
<br class="">
Can this be fixed? Sure. We could add support for beta versions to `@available`, or fake it somehow with the existing version syntax. But in both of these cases, it means you have to know what constitutes a "release", so that you can be sure to use a higher number than the previous "release". This could be made to work for a single library, but falls down for an entire Apple OS. If the Foundation team wants to add a second new enum case while macOS is still in beta, they're not going to stop and recompile all of /System/Library/Frameworks just to try out their change.<br class="">
<br class="">
So, availability ordering is great when you have easily divisible "releases", but falls down when you want to make a change "during a release".<br class="">
<br class="">
<br class="">
Salvaging Availability Ordering?<br class="">
<br class="">
- We could still sort by availability, so that you can reorder the sections but not the individual cases in them. That doesn't seem very useful, though.<br class="">
<br class="">
- We could say "this is probably rare", and state that anything added "in the same release" needs to get an explicit annotation for ordering purposes. (This is equivalent to the `@abi(2)` Dave Zarzycki mentioned in the previous thread—it's not the default but it's there if you need it.)<br class="">
<br class="">
- We could actually require libraries to annotate all of their "releases", but in order to apply that within Apple we'd need some translation from library versions (like "Foundation 1258") to OS versions ("macOS 10.11.4"), and then we'd still need to figure out what to do about betas. (And there's a twist, at least at Apple, where a release's version number isn't decided until the new source code is submitted.)<br class="">
<br class="">
- There might be something clever that I haven't thought of yet.<br class="">
<br class="">
<br class="">
This kind of known ordering isn't just good for enum cases; it could also be applied to protocol witnesses, so that those could be directly dispatched like C++ vtables. (I don't think we want to restrict reordering of protocol requirements, as much as it would make our lives easier.) So if anyone has any brilliant ideas, Slava and I would love to hear them!<br class="">
<br class="">
Jordan</blockquote><div class=""><br class=""></div><div class="">Kind of a hybrid idea, but hopefully one that circumvents the internal issues that you outline here and simplifies the mental model. I'll introduce it stepwise:</div><div class=""><br class=""></div><div class="">Currently, the @available annotation is supported for platforms and for Swift versions; you propose extending support to arbitrary deployments (e.g., MagicKit). Instead, suppose you extended support to arbitrary versioned types (open, public, and @_versioned internal):</div><div class=""><br class=""></div><div class="">@_versioned(abi: 2)</div><div class="">public enum SpellKind {</div><div class=""> case hex, charm, curse</div><div class=""> @available(abi: SpellKind 1) case blight</div><div class=""> @available(abi: SpellKind 1.1) case jinx</div><div class="">}</div><div class=""><br class=""></div><div class="">Now, clearly, the value of "abi" is arbitrary inside the @_versioned annotation; it's not really necessary for our limited purposes, and if there's a typo and it's lower than the highest ABI version referenced in an @available annotation, things get wonky. So, drop it:</div><div class=""><br class=""></div><div class="">public enum SpellKind {</div><div class=""> case hex, charm, curse</div><div class=""> @available(abi: 1) case blight</div><div class=""> @available(abi: 1.1) case jinx</div><div class="">}</div><div class=""><br class=""></div><div class="">This is looking like the original @abi(2) proposal that Dave Zarzycki brought up. However, a key difference here: multiple cases can have the same ABI "version" and would be ordered relative to each other by name; that is, a user would only be annotating when new cases are added and doesn't have to think about memory layout; Swift takes care of the rest.</div><div class=""><br class=""></div><div class="">This can be simplified further; these ABI version numbers are entirely arbitrary. Suppose we instead extended the "@available(introduced:)" syntax to allow dates or timestamps:</div><div class=""><br class=""></div><div class="">public enum SpellKind {</div><div class=""> case hex, charm, curse</div><div class=""> @available(*, introduced: 2017-09-30): case blight</div><div class=""> @available(*, introduced: 2017-10-12): case jinx</div><div class="">}</div><div class=""><br class=""></div><div class="">I suspect there are wrinkles to this scheme, but the overall idea here is to salvage availability ordering but have some way to version a type in a low-mental-overhead way instead of resorting to a syntax for manually ordering cases.</div><div class=""><br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div>Pretty much. If you want a stable order, you need to manually annotate each change to the enum’s layout with some incrementing identifier which can be sorted. Ideally, we would use the module’s version number, but as Jordan points out, during development layout can change even between versions.</div><div><br class=""></div><div>So the simplest answer to me is to give each enum it’s own mini version number. You could write them out, as in your examples. Another approach might be to introduce a version-break statement in the case-list, with the condition that those version-breaks cannot be reordered, but everything inside of them can be:</div><div><br class=""></div><div>enum SpellKind {</div><div> case hex, charm, curse</div><div> @new-version case blight</div><div> @new-version</div><div> case jinx</div><div> case summoning</div><div> case ...</div><div>}</div><div><br class=""></div>A library developer could add as many of those as they need for internal testing, and selectively remove them as appropriate for each Beta/GM release (or they might keep them, if they decide to promise binary compatibility between beta and GM).</div><div><br class=""></div><div>- Karl</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div></div></div></div>
_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-dev<br class=""></div></blockquote></div><br class=""></body></html>