Nickolay Tarbaiev
Nickolay Tarbaiev
Another workaround is searching for the missing symbols on GitHub, then building them for arm64 simulator and merging them together using `libtool`. This way I successfully patched MLKit, which had...
Might be helpful to someone. In my case I used the issuer ID from another account (because I copy-pasted the json 🤦). It was very hard to notice as they...
@notcome given the Combine and Swift Concurrency interoperability and switching from `Publisher` to `AsyncSequence`, I think `AsyncAlgorithms`'s behavior should be consistent with `Combine` as much as possible. I had to...
@FranzBusch Thanks for the update! However the PR does not seem to be addressing this issue. The `AsyncThrottleSequence.next()` is still awaiting the next element of its base sequence even after...
A side topic, but I was somewhat surprised to see a 1.0.0 release already. There is no description or a changelog for it. Just wondering, are there some breaking changes...
>One confusing factor is that all AsyncSequences are applied as a demand of 1; in that each call to next is what drives the production of values. This comes in...
I think the issue might be caused by accessing the Future's `result` from the `Conduit` from outside of the Future's `lock` [here](https://github.com/OpenCombine/OpenCombine/blob/1c6f02c7ed8140c0ba7a783aaddb6e0685a0037b/Sources/OpenCombine/Future.swift#L185). Strangely neither the Address nor Thread sanitizers are...
Definitely the implementation, both Combine and OpenCombine. I spent a weekend investigating this exact issue.
@natecook1000 Thanks for your notes. I had some doubts about the design. However also tried to keep the changes minimal. I always appreciate flexibility and customization options in API's. And...
Hi @natecook1000, It's been a year since I proposed this feature and not sure how to proceed with it. The #4 and #41 you mentioned before have had no significant...