Rick Newton-Rogers
Rick Newton-Rogers
Yep, sure.
This should resolve https://github.com/apple/swift-async-algorithms/issues/247
Forums post on this https://forums.swift.org/t/swift-async-algorithms-proposal-produce-empty-chunks/72575
Thanks for the approvals all. I'm not sure we should actually merge it though since the build is failing in some C components.
@guoye-zhang the workflows have surfaced issues when building against the Static SDK, presumably we'd like to get those fixed before enabling the workflow? https://github.com/apple/swift-openapi-urlsession/actions/runs/15927028444/job/44926577967
Hi! Thanks for filing this issue. I am currently taking a look into this problem to see if I can come up with a fix in the short term, however...
Thanks for getting in touch! QWACs are interesting but I'm afraid they aren't one of our short term priorities. Contributions are always welcome though if you or anyone else are...
I was able to create a minimal reproducer of this issue and I believe it is indeed linked to `BUILD_LIBRARY_FOR_DISTRIBUTION`. Unfortunately when I took a quick Look at working around...
Thanks for filing this issue, I believe that the API is public and available to use, just behind SPI - is that correct? At the moment there are SPI guards...
Which objects are you trying to access?