Nate Foster comments

Results 224 comments of


                                            Nate Foster

Should it be legal to have a reference of an extern type name within the definition of that extern?

Changes needed to close this issue. - `p4c` needs to be updated to not reject these programs. - We might also consider modifying the spec to clarify that this is...

Clarification regarding Exit statement

> There may be a registered callback (analogous to a default action) that gets invoked to process the exit result (see man exit) This is what happens in P4 too....

remove overflow warning when using signed integer literals of same representation size?

I agree that the comments in the spec look wrong. Do you want to submit a PR fixing it? We can discuss it at the January LDWG meeting.

remove overflow warning when using signed integer literals of same representation size?

Thanks! We'll discuss this at January's LDWG.

Introduce local compile-time known values

@apinski-cavium, actually, I had inverted the definitions -- local compile-time known is more restrictive. See my latest commit which fixes this and adopts your streamlining suggestions.

Introduce local compile-time known values

Anyone else have comments or suggestions on this one?

Introduce local compile-time known values

Any further comments on this or should we merge it?

Introduce local compile-time known values

Sure. Can you provide a pointer to those questions? I might be missing something but I don't see them in the conversation on this issue.

Introduce local compile-time known values

Here is a small example showing what `p4c` does. ```p4 control C(inout bit x); package P(C c); const int f = 42; int g(int x) { return x; } control...

Introduce local compile-time known values

@jonathan-dilorenzo this is ready for you to take a look.