Inconsistency between Remotable rules and InterfaceGuard pattern language

[erights]

Now migrated to endojs/endo#1728 . Further discussion should happen there.

---

agoric-sdk/packages/notifier/src/publish-kit.js

Lines 48 to 53 in 61b6c39

	export const IterableEachTopicI = M.interface('IterableEachTopic', {
	subscribeAfter: SubscriberI.methodGuards.subscribeAfter,
	[Symbol.asyncIterator]: M.call().returns(
	M.remotable('ForkableAsyncIterableIterator'),
	),
	});

Remotables are allowed to have symbol-named methods. (The particular case that is already important for us is Symbol.asyncIterator as we see here.)

InterfaceGuards are supposed to be Passable descriptions of the API of an exo, including the guards and methods used do the first level of input validation of the exo's methods. The InterfaceGuard uses a CopyRecord of method guards, where each property name of that CopyRecord is supposed to be the name of the method being described/guarded.

However, a CopyRecord can only have string-named properties. Therefore, there is currently no way for an InterfaceGuard to provide a MethodGuard for describing/guarding a symbol-named method.

[erights]

Since endojs/endo#1728 is closed, I'm closing this one. However, note that agoric-sdk is not yet updated to depend on an endo incorporating this fix.

cc @gibson042