read-only), which can be overridden with custom getters and setters
in the class.
-Methods can be specified as read-only; a read-only version of the
-interface is then generated, and a secure read-only reference to an
-object can be generated that can only access read-only methods. This
-would save effort declaring a separate interface and a separate
-class, and would allow the read-write interface to use the read-only
-methods without retreiving the read-only object.
-
Implement marshalling/unmarshalling stubs.
Implement async methods.
can only be used when invoked as a sync in-process method; the method
implementation can check to see how it was invoked, and use the out
parameters to avoid having to make a completion callback.
+
+Use linker section garbage collection to discard GUIDs, vtables, etc. for
+interfaces/vstructs that aren't referenced.