Max Howell
Max Howell
So basically: not a bug (we're running up against the limitations of the platforms we run upon). But we should try to not trigger it if we can figure out...
I like this. Perhaps a way to (further†) ensure the chaining only happens where the user expects is like so: ```swift defer { episode.dispatcher.retire() } episode.updateMediaSize().then { didSetSize in episode.updateMediaAttributesIfNeeded().map...
I imagine a multiple line attempt would be ambiguous, but possibly not (hopefully not). In general one must do multiple line attempts since one liners are inferred differently (and more...
Seems cool. Can we make tests pass?
If we can base this onto v7 we can get it in.
Merge conflicts.
CI did not run (GitHub Actions bug perhaps) we need that to verify that the changes do not cause ambiguity. Even then I am concerned about the change of `cancellableWhen`...
I'm disabling this test since it is interfering with dev.
Probs doesn’t need to hold up v7 though, or you think otherwise?
Like, I believe I can tag 7.0.0 as it stands.