+ Or foo..something() ??
+ Maybe if type of first arg is compatible, the value before '.' is interpolated
+ unless ".." is used.
+
+ So the name after "." can:
+ - follow a pointer
+ - be field in struct/record
+ - follow a transparent field
+ - be constant in type - which includes functions.
+
+ Transparent fields add extra distance and a closer name will match first.
+ So if foo.bar and foo.baz.bar are both valid and baz is transparent, then
+ "foo.bar' gets the former - no conflict is reported. Obviously foo.bax.bar
+ gets the latter
+
+Methods can be added to values to provide required interface for passing to
+a function. This probably only works for references.
+We can specify the methods using a type which includes them, or a value
+which already has them, or individually
+Syntax might be tricky. For 'sort' I want to pass an array, and a method
+for comparing two elements of the array. I want the function to see an array
+where the element are already comparable.
+So the function declares that it needs a type
+
+ func qsort(type:comparable, target:[size::]type)
+
+function will need size of members of array, size of array, and compare function.
+ func qsort (target:[size::]type:comparable)
+
+ ra:[32]int
+ qsort(ra, :ra[].cmp(a, b) = a >= b)
+
+Same syntax could add a destructor
+
+ foo: bar .free = myfunction