Lee Byron

Yeah - I think these functions definitely deserve to belong on both typical and async iterators (should those reach stage 4) - not sure if that should be two separate...

Thanks for the suggestion and the idea! I agree with the problem and your solution is pretty interesting. I'll take it into consideration!

Excellent feedback. I'll do some research.

Of course I also pretty strongly agree with you, @loganfsmyth - that's why I pitched the proposal in the first place. I agree that the potential for confusion is really...

> The last minute changes to #775 I'm sorry about that! My intent was to factor these out from #777 and land and rebase, but this one got additional editorial...

This definitely clarifies, but maybe we need to back up and define some terms to expand this. We use the terms "inner type" and "wrapped type", and "unwrapped type" interchangeably...

Sorry for letting this one sit - I think this is one of our last meaty editorial changes before we're cut-ready. --- I'd love if we can keep the name...

> **Wrapped type**: a type that wraps another type, instance of List/Non-Null, e.g. `Int!` > > * **list wrapped type**: instance of List, e.g. `[Int]` > * **non-null wrapped type**:...

Thoughts: Since Kotlin is the precedent for this behavior, consider they [deprecated "experimental" in favor of optin](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-experimental/) Perhaps: ```graphql directive @optIn(feature: String) ``` Where elements with this directive are not...

This is a really interesting proposal, thanks for writing it up. I'm curious if you're finding cases where you couldn't express something correctly before, or if this is just purely...