Send and receive Remotable tags #1628
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelfig
approved these changes
Aug 27, 2020
This was referenced Aug 27, 2020
erights
force-pushed
the
transmit-ifaces
branch
from
5dd4aa1 to
cd90a3c
Compare
erights
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempting progress on the #804 plan.
Tag ERTP brands with allegedName as "interface". Should reappear on remote presence of brand.
As a temporary measure, until we get petname-based rendering in the repl, we currently require all string ifaces to be either 'Remotable' or to start with 'Alleged: ', since the name (e.g., brand name) is only according to the object itself and we have no other way to urge caution in reading too much into these. This is temporary.
Residual TODO #1631