Event JSON
{
"id": "51c26f22b814cfc37a9945247c4feffbf8dda5f595bca1d5fb6410a4e257997c",
"pubkey": "2ee6dac009c8e0fce62a16ee0a81b96a7b93dc38158fde7c36ea7fa21689a93c",
"created_at": 1710320155,
"kind": 1,
"tags": [
[
"p",
"ba4d17a48270c1ebffa3f62fa129d85092a4874c9f0c4f768d88911631cc5d76",
"wss://relay.mostr.pub"
],
[
"p",
"f8f0140816fffbd0d9b0dc7029100665def9f00b34774494393c3a036779381f",
"wss://relay.mostr.pub"
],
[
"p",
"326c9100a3d1f1ecd0d35bf9590b2633e6c22a25debb08aac79d5af903bd8672",
"wss://relay.mostr.pub"
],
[
"proxy",
"https://mastodon.social/users/tonyarnold/statuses/112087541688196732",
"activitypub"
]
],
"content": "I agree with nostr:npub1hfx30fyzwrq7hlar7ch6z2wc2zf2fp6vnuxy7a5d3zg3vvwvt4mq34evlg in his post on the forums: https://forums.swift.org/t/asyncstream-and-actors/70545/4\n\nMy take: Swift Concurrency has gone from being somewhat understandable to being really, really hard to apply and understand properly. \n\nI get that we can stick with Swift 5 language mode, but none of us *wants* to do that. \n\nI hope that WWDC brings some understandable instruction alongside improved tooling, because right now we're all reliant on nostr:npub1lrcpgzqkllaapkdsm3czjyqxvh00nuqtx3m5f9pe8saqxeme8q0stj8c9v sharing what he has worked out (thanks Matt!).",
"sig": "0aa47182a139b132784ac71fa6ebdba28b1dfa3b2d97293c7c02a01bf5049a2485cc33769d496bea8602a1d933dd4a756ae25a821c0da29759d242b8ed1ce7bd"
}