Index: doc/proposals/tuples.md
===================================================================
--- doc/proposals/tuples.md	(revision 7ef4438154228273f1e40137bc17a3cd20e74ce5)
+++ doc/proposals/tuples.md	(revision 5485bcacfaeb40fe5a8bbc0bad1dcacc01cf7608)
@@ -240,4 +240,16 @@
 allow restructuring when the type is passed as a type value. This may be
 the most correct form, but seems surprising compared to the common use.
+
+### Tuple Arrays Not Supported
+
+You cannot make an array of tuples. For some reason the type just will not
+work. Thoretically it could, each tuple type has a size and alignment and
+could be put in an array. However the following type is not accepted:
+
+	[int, char] array[3] = {{1, 'a'}, {2, 'b'}, {3, 'c'}};
+
+Now the opposite, a tuple containing an array, does actually work:
+
+	[int[3], char] data = {{1, 2, 3}, 'd'};
 
 ### Unary Tuple Value Syntax
@@ -539,4 +551,22 @@
 	([int, int, int])tuple_int_int;
 	([long, [float, int]])tuple_long_float_int;
+
+### Tuple Array Support
+
+Arrays of unstructured tuples/packs are not actually required, an array of
+structures will store the data just as well and this is not the transient
+context where the unlabeled tuples work well. So it would work fine to
+not allow an array of packs, but if we do not a better error should be
+created.
+
+All that being said, the following could just work.
+
+	[int, char] u_array[3] = {...};
+
+What should definitely work is an array of struct tuple, because that should
+work where a generic structure could be used. This is also part of why arrays
+of packs are not needed.
+
+	tuple([int, char]) s_array[3] = {...};
 
 ### New Tuple Literal Syntax