keyword-generics-initiative
keyword-generics-initiative copied to clipboard
rust-lang
Public repository for the Rust keyword generics initiative
Current async changes the return type of function to `impl Future`, same way as generators, etc. This requires effects to provide a GAT return type and involves pinning. For the...
## todos - [x] discuss what happens when pattern types don't subtype (e.g. constraining return types would not be backwards-compatible) - [ ] discuss the XOR relationship between `no_panic` and...
Finally got around to reading #54 and I think that golang's `go` keyword should be mentioned as a direct alternative to `async let` from Swift. They perform similar operations, and...
If you consider the `extern "ABI" { ... }` as describing a particular (foreign) function color, then it seems fairly natural to model them in an effect system. Would this...
https://github.com/rust-lang/keyword-generics-initiative/blob/master/charter.md#membership https://github.com/rust-lang/keyword-generics-initiative/blob/master/design-questions/README.md
We renamed the initiative to: "the effects initiative", and our Zulip stream is `t-lang/effects`. We should probably rename this repo to `rust-lang/effects-initiative`. cc/ @oli-obk I believe you can do that?
One thing that was rather unclear to me when reading the draft RFC is whether implementations of traits must be exclusive (e.g. you can only implement sync *xor* async) or...
## Opinion I stumbled upon this repo as a complete outsider, and one of the things that stood out to me was the syntax. Taking an example from the book:...
I just finished reading [Yoshua's Article on Totality](https://blog.yoshuawuyts.com/totality/), which got my thinking more about this proposal and its potentially massive implications for future versions of Rust. Is the desire for...
imho it'd be useful for code to be able to be generic over mutability. related: https://github.com/rust-lang/rfcs/issues/414
