🚀 go-pugleaf

  I would like to complain about opaque types being pointers only. When I teach
ADTs, I teach a Table, with a few operations that manipulate cursors (a unifi-
cation of indexes and pointers).  One can locate an element and get a cursor;
one can use the cursor to retrieve/update information from/to a table.  The
definition module of the Table ADT exports opaquely the cursor type.  One
implementation of Table uses arrays, where the cursor type is integer.  Another
implementation uses pointers for cursors.

  This example will be impossible with the new standard.  Couldn't one say
that opaque types must allow for the largest of all the primitive (so called,
one-word) types?  What is the rationale for restricting it to pointers only?

Rich
-------