Dan Stenmark

Seeing these same errors as well when trying to pull in the Charts library (4.1.0) via Carthage. We're building this as part of an SDK we distribute, so we require...

It seems that decorating the culprit Sequences and Collections (e.g. `AdjacentPairsSequence`, `AdjacentPairsCollection`, etc) with the `@frozen` modifier fixes this. Alas, ABI Stability isn't quite my forte. @natecook1000 @xwu and anyone...

@matopeto This PR does not fix the issue. After testing this out myself, I've determined that the problem originates from Algorithms and its lack of ABI stability. I've opened up...

As far as I can tell, the two potentials paths forward are: 1) Work with the Algorithms folks to make the library ABI stable (e.g. annotating their generic structs with...

> @djs-code the PR fix the issue, but you have to build the package with plain carthage without injecting BUILD_LIBRARY_FOR_DISTRIBUTION to the carthage (because it inject also for algorithm) >...

@matopeto What about when the Cartfile also includes SnapKit, MarkdownKit, and/or SwiftOTP? We pull in these libraries via Carthage as well, and we need `BUILD_LIBRARY_FOR_DISTRIBUTION` enabled in each one. Even...

@matopeto That workflow is not going to be practical for most folks, and I would generally regard it as bad developer experience. Unforunately, I'm sad to say that https://github.com/danielgindi/Charts/pull/4912 is...

@pmairoldi Based on the PR history, it looks like you've been the most active maintainer here in recent times. Do you have any thoughts on this?

@pmairoldi We distribute a pre-built binary framework that depends on Charts (among other libraries), which we ask our users to pull in via Cocoapods or Carthage. Unfortunately, while our clients...

@pmairoldi #4912 Does not fix this issue, for the reasons described earlier in this thread.