restore safe runtime functionality - #159
Draft
statusfailed wants to merge 1 commit into
Draft
Conversation
... using only public exposed Runtime API
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
... using only public exposed Runtime API
I haven't carefully reviewed the output here; this is mostly intended as a check that one can write the safe runtime against the (new)
RuntimeAPI, which should be agnostic to concerns like IPC, etc.The intent is that safe runtime can be built fully 'on top' of runtime, and that runtime's public API is sufficient without having to expose any internal details.