[banjo] Require enum declaration to set a value
The parser grammar accepted enum declarations without an explicit value, but the AST processing does not. We intend to enforce FIDL-like behavior of requiring all such declarations to have a value, so this change modifies the grammar to reflect this. Change-Id: Ieaa5e0f5dbd40f5b78341be3c626a3e073709328
Showing
- tools/banjo/banjo/src/ast.rs 2 additions, 2 deletionstools/banjo/banjo/src/ast.rs
- tools/banjo/banjo/src/backends/c.rs 2 additions, 2 deletionstools/banjo/banjo/src/backends/c.rs
- tools/banjo/banjo/src/parser.rs 2 additions, 2 deletionstools/banjo/banjo/src/parser.rs
- tools/banjo/banjo/test/ast/callback.test.ast 4 additions, 4 deletionstools/banjo/banjo/test/ast/callback.test.ast
- tools/banjo/banjo/test/ast/enums.test.ast 40 additions, 40 deletionstools/banjo/banjo/test/ast/enums.test.ast
- tools/banjo/banjo/test/ast/example-4.test.ast 1 addition, 1 deletiontools/banjo/banjo/test/ast/example-4.test.ast
- tools/banjo/banjo/test/ast/example-9.test.ast 2 additions, 2 deletionstools/banjo/banjo/test/ast/example-9.test.ast
- tools/banjo/banjo/test/ast/interface.test.ast 3 additions, 3 deletionstools/banjo/banjo/test/ast/interface.test.ast
- tools/banjo/banjo/test/ast/protocol-other-types.test.ast 1 addition, 1 deletiontools/banjo/banjo/test/ast/protocol-other-types.test.ast
- tools/banjo/banjo/test/ast/simple.test.ast 4 additions, 4 deletionstools/banjo/banjo/test/ast/simple.test.ast
- tools/banjo/banjo/test/ast/types.test.ast 9 additions, 9 deletionstools/banjo/banjo/test/ast/types.test.ast
Loading
Please register or sign in to comment