P4 formalization #442
Open
P4 formalization #442
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
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.
A stand-alone (yet incomplete) draft of the formalized spec. This version is consistent with our discussion for the P4 workshop and follows the informal and formal format of web assembly spec. The goal is to provide a simple formalization along with an informal description of the type system and guidance on how to implement it.
The readme in docs/petr4spec explains how to build the spec.
Feedback is appreciated. I highly recommend trying to put yourself in the developers' shoes while reading it by relying more on the informal description to guide you through the formalization and see if the informal format actually helps you understand the type system to the extent that you'd be able to implement it.