Nate Foster

If we are brainstorming syntax, how about using curly braces (or any other kind of brace... could be `< ... >` or `{| ... |}` for example) to denote an...

Fair. But as the person who creates the releases of the spec, let me beg all authors to include a ChangeLog. It's very painful for me to recreate them from...

If the token is `{#}` then it cannot be the first character of the line... Generally, tokens are indivisible. For example, the following is not legal P4: ```p4 co nt...

If `#` only ever has meaning when it appears immediately within a set of curly braces, then I think `{#}` should be a token... This is a trivial front-end change....

My knee-jerk reaction is that I prefer to keep terms that provide some new feature (e.g., invalid headers, struct literals, etc.) separate from terms that convert types (e.g., casts). We...

I don't really care about the concrete syntax. My wish was to separate constructs that denote polymorphic literals like invalid headers from casts, and to do this consistently throughout the...

The problem with #1220 and #1218 from my perspective is that they require a cast to appear along with the invalid header.

First, one is not obliged to use the no-namespace import. So you can do that if it's safe and convenient. If there are clashes, then you do ``` import MyMegaModule...

P4 is not an object-oriented language though, so it's not clear that borrowing ideas about code reuse from that paradigm is best. I think we should not slow down the...

In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open...