Niko Matsakis
Niko Matsakis
@Diggsey > This is... a lot to take in. I think it is a lot less to take in than it may appear. I view this RFC as documenting existing...
OK, I want to engage more deeply on the naming question. It's important and I don't think color is necessarily optimal. Here are some thoughts. When it comes to names,...
@rpjohnst I'm thinking more about this... > My point is really that "effect" need not imply anything so deep about the language that it does not already apply to Rust,...
Responding to my response to @Diggsey, @GoldsteinE wrote... > I feel like `async Read` is the confusing part. `Fn` is already a deeply magical trait, having a magic translation to...
@Diggsey You would import `Read`, yes, and you would write `dyn async Read`, just as (under RFC #3668) you write `dyn async Fn()`. > If they all share the same...
OK, I've pushed through some 'surface level' changes. * I adopted "flavor" and rewrote the FAQ to explain the reason it was chosen (building on the text I wrote above)....
@michaelwoerister, think you'd be up for that? =)
@mark-i-m starting with that seems ok =)
One other suggestion: the (experimental) project goals process is meant to be a good framework for ambitious projects like this one. You could try authoring a project goal (see rust-lang/rust-project-goals)...
just writing `match { }` would indeed work as syntactic sugar for `|x| match x { }`. I don't believe there is an ambiguity there, because we don't currently permit...