🚀 go-pugleaf

In article <u71z1icf9a.fsf@o2-3.ebi.ac.uk>,
Philip Lijnzaad  <lijnzaad@ebi.ac.uk> wrote:
>this is essentially the same as your struct  ...

No. The essential difference is that you can access a valuetype
on the language level in a polymorphic way, whereas you have to
unpack an any in a much more complicated procedure. Please note
that the subject is "extensible structs" - valuetypes are the
interoperable version of that, not the any type.

>Martin>    valuetype hash{
>Martin>      private sequence<item> items;
>Martin>      public ValueBase get(in string key);
>Martin>      public void set(in string key, in ValueBase value);
>Martin>    };
>
>... and this is essentially the same as your interface, with the added
>inconvenience that the client will have to implement get and set, and that
>transmitting all the items maybe impossible due to bandwidth  ... 

No. The essential difference is that all invocations will be local,
as opposed to being remote - which is an essential difference if
you have a large number of items.

Regards,
Martin