Will Hawkins d33066c543 compiler, runtime, testing, common: Centralize Execution/Evaluation
Centralize the execution of statements and evaluation of expressions
so that the user can specify a debugging "callback" after every
execution/evaluation.

The callback can be used for myriad things, but it seems likely that
it will be useful for implementing:
1. Testing
2. Debugger

Signed-off-by: Will Hawkins <hawkinsw@obs.cr>
2026-04-20 05:53:43 -04:00
2026-02-24 01:00:32 -05:00
2026-01-23 23:51:49 -05:00
2026-03-06 07:47:05 -05:00

P4RSE: P4 Runtime In Swift Environment

P4RSE (yes, the acronym is a bit forced) is a P4 parser and runtime written in Swift. The project was started as a means to better learn Swift.

Status

Very, very alpha:

  1. Limited parts of the language can be parsed.
  2. Limited programs can be evaluated.

As an example of what can be parsed and evaluated, here is a fairly complex P4 program cobbled together from our unit tests:

control simple(bool x, bool y) {
  action a(int z) {
    z = false;
  }
  table t {
    key = {
      x: exact;
      y: exact;
    }
  }
};
struct Testing {
  bool yesno;
  int count;
};
parser main_parser() {
  state start {
    Testing ts;
    ts.count = 1;
    transition select (ts.count) {
      0: accept;
      _: reject;
    };
  }
};

Please check back often!

Building

Requirements And Basic Build

This project uses code item macros (CodeItemMacros) which are an experimental feature in Swift and not available in production.

Therefore, to compile this project, you must be using a non-production version of the compiler.

With that caveat noted, building can be done with swift build:

$ swift build

Contributing

We would love your help! Contributions are very welcome!

Coding Style

Here are the style guidelines that we are trying to maintain:

  • variables are in snake_case.
  • types are in CamelCase.

Of course, we want to follow the formatter, too: see below.

Commit Messages

We will try to maintain the following headline format for commit messages:

<component>: <subcomponent>: <change>

where <component> is one of:

  1. grammar: For the tree-sitter-based grammar.
  2. compiler: For the Swift-based P4 compiler of tree-sitter-based-parser parsed programs into AST.
  3. runtime: For the Swift-based P4 interpreter.
  4. common: For any Swift-based components common to the entire project (and macros).
  5. documentation: For any documentation updates.
  6. testing: For Swift-based tests.

where <subcomponent> can be more free-form and <change> is a pithy description of the changes in the commit.

Testing

To run the P4RSE tests:

$ swift test

To run the parser tests, from the tree-sitter-p4 directory:

$ npx tree-sitter test

Generating Documentation

To build the documentation:

$ swift package generate-documentation

To preview the generated documentation:

$ swift package swift package --disable-sandbox preview-documentation  --target <some target>

For more information, see the documentation for the Swift-DocC plugin.

Checking Format

To check the format:

$ swift-format --recursive -i Sources/
S
Description
No description provided
Readme GPL-3.0 1.3 MiB
Languages
Swift 88.3%
JavaScript 10.7%
P4 0.9%