Lists of capabilities not implemented yet

[talex5]

If you define a schema with List(Interface) then:

1. The types are wrong: it gives e.g.
   val a_get_list : t -> [`Interface_xxx] list
   instead of
   val a_get_list : t -> [`Interface_xxx] Capability.t list
2. The implementation generated is failwith "not implemented (type iface)".

As a workaround, you can use a list of structs containing interfaces instead.

[avsm]

Thanks; just for the record, I ran into this while implementing https://github.com/avsm/ocluster/blob/4cfd39f91a0349d02851c0f0cac8e338bc17715b/api/cluster.capnp#L27

[joprice]

Is -> stream also unimplemented? I get an error like the following when I try it:

12 |   module Stream_9710718097904890872 : Stream.S with
                                           ^^^^^^^^
Error: Unbound module type Stream.S

[joprice]

The docs mentioned handling this is a client side responsibility, so maybe this is actually a codegen bug.

Currently, flow control is only implemented in the C++ library. RPC implementations in other languages will treat -> stream the same as -> () until they add explicit support for it.