Xcode 11 beta 2/3 fails to compile about swift-nonempty HOT 6 CLOSED

Filed with the fruit company as FB6699142. I'll report back if I hear anything.

from swift-nonempty.

Same here, and also in stable Xcode.

Catalina beta3
Cocoapods 1.7.4
both Xcode11 beta 3 + 11commandlinetools and Xcode10.2.1 + 10.2.1commandlinetools

from swift-nonempty.

I've had the same build error on Catalina and Xcode 11 beta 3, as well as Mojave and Xcode 10.2.1. I'd be happy to open a PR but I'm not sure where to start. My build error's very similar to @ilyapuchka's, only shorter. The most important lines of the error, it seems like, are

*** DESERIALIZATION FAILURE (please include this section in any bug report) ***
result not found
Cross-reference to module 'NonEmpty'
... NonEmpty
... in an extension in module 'NonEmpty'
... SubSequence

Stack dump:
[...]

1. While deserializing SIL function "$s8NonEmptyAAVyxGSMAASMRzrlSM6swapAtyy5IndexQz_AFtFTW"
2. While reading from 'NonEmpty'
3. While finishing conformance for protocol conformance to 'MutableCollection' (in module 'Swift') for type 'NonEmpty<C>'

This alludes to the problematic file being NonEmpty+MutableCollection.swift. If that file's removed from the target, the project builds. I haven't gotten results more granular than that.

NonEmpty build deserialization failure - Xcode11b3.txt

from swift-nonempty.

This is happening to me on Xcode 11 stable release also 😞 Do you have any news on this?

from swift-nonempty.

Well, apparently I got a bit carried away on #22, and the "fix" only worked on incremental builds 😓, which is no different from the current version (which fails to compile on clean builds, but works the second time).

Sorry for the noise 😇

UPDATE: After much experimentation, I think I've found a fix that works even on clean builds. It consists of making NonEmpty conform to Collection right from the declaration, instead of in an extension. Not sure why this fixes it though 🤷‍♂

from swift-nonempty.

If this actually fixes the bug (as I hope), we should probably open/mirror the bug over at https://bugs.swift.org for better public visibility. We already have the "hardest" bit, which is a working PoC 😄.

@loganmoseley do you know if it has been mirrored already?

from swift-nonempty.