From 7be73b6ebc43046e771981162ad073e73bf6da58 Mon Sep 17 00:00:00 2001 From: Taylor Cramer Date: Mon, 27 Feb 2017 23:01:23 -0800 Subject: [PATCH] Fix unresolved questions bulletpoints --- text/0000-variadic-generics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/text/0000-variadic-generics.md b/text/0000-variadic-generics.md index 37c5d7a74b3..94593c4ceae 100644 --- a/text/0000-variadic-generics.md +++ b/text/0000-variadic-generics.md @@ -201,14 +201,14 @@ unified `Tuple`. # Unresolved questions [unresolved]: #unresolved-questions --It might be useful in the future to expand on the locations where `...Type` +- It might be useful in the future to expand on the locations where `...Type` can be used. Potential extensions to this RFC could allow `...Type` in non-tuple generics or in function argument types, like `fn foo(args: ...Args)`. This would allow functions and traits to use variadic generics without explicit tuples. This could enable things like the proposed `foo[i, j]` syntax using`Index`. --Should the `Tuple` trait use separate `TupleRef<'a>` and `TupleMut<'b>` traits +- Should the `Tuple` trait use separate `TupleRef<'a>` and `TupleMut<'b>` traits to avoid dependency on ATCs? It seems nicer to have them all together in one trait, but it might not be worth the resulting feature-stacking mess.