Stephen Celis

@tgrapperon Thanks for this! @mbrandonw and I decided to flesh out our current vision for 1.0 here: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477 This includes a plan for simplifying the `Effect` type. In the discussion...

(Oh, and if you do have things you wanna share, @JacksonUtsch, sorry to put more pressure on you to do so before 1.0, though if you don't have time to...

The reception to the change has been positive, so we're going to move forward with this. Thanks again @tgrapperon!

Thanks for looking into this! @mbrandonw and I chatted about it today and we think the main thing missing would be to tie the storage to `DependencyValues` instead of a...

@rmosolgo Fair point! This kind of concurrency could definitely be used independently of `graphql-batch`! The individual resolver layer benefits (as in the mutation example above) and, though I haven't dug...

@rmosolgo We could move this discussion to https://github.com/rmosolgo/graphql-ruby or Slack if you'd like to discuss more! Definitely some interesting gains to explore.

@dylanahsmith Yep, sorry, this conversation started concurrently with that one 😉 I need to familiarize myself a bit more with `Executor` and other internals to see what's needed and hopefully...

Hey, sorry about that! Looks like you're hitting a compiler crash, which would be useful to share with the Swift core team. Can you give us more information about your...

Hey @innoreq! Some of the docs are a little outdated since this is a project mostly used by us and not a library we expect there to be many users...

@innoreq You may need to fork the repo if you made changes locally. Alternately you could copy the local README and paste it into GitHub's editor.