Manlio Perillo

@ibokuri `0.12.0-dev.2341+92211135` now returns an error message: ```console test.zig:28:51: error: unable to resolve inferred error set of generic function pub usingnamespace Writer(@This(), Ok, Error, write); ^~~~~ test.zig:34:9: note: generic function...

See also the pending #80, where the same issue is fixed in https://github.com/ziglang/zig.vim/pull/80/commits/03d19a6ec31b66725242e7f649455d2515770735.

@Vexu, the grammar still fails with some source file in the `zig` project. Using the script https://gist.github.com/perillo/a1a731d234b425597a70412a7343b772, these are the errors: ## compiler source `./parse.sh ../../zig/src/**/*.zig`: ``` parsing 128 files......

@Vexu, found more errors when checking the `zig` test suite: ## Compiler tests `./check_parser.sh ../../zig/test/**/*.zig`: ``` running 1456 tests... FAIL: ../../zig/test/behavior/decltest.zig: zig: 0, grammar: 1 :5: syntax error test t...

In addition to number literals, the zig parser seems to be able to do additional analysis compared to `grammar.y`, in order to handle ambiguous cases. `./check_parser.sh ../../zig/test/**/*.zig | grep "zig:...

Do you think they should be documented in the Zig Language Reference?

@Vexu, in order to check the *PEG* parser I wrote a tool (in *Go*, since it was more convenient) that downloads up to 1000 repositories using the GitHub API, and...

Found other issues: - [ ] Not sure where is the problem ```zig pub const DmaTuple = struct { DmaController(0), DmaController(1), DmaController(2), DmaController(3) }; ``` https://github.com/paoda/zba/blob/main/src/core/bus/dma.zig ``` check https://github.com/paoda/zba/blob/main/src/core/bus/dma.zig :...

What is strange is that the Eowyn workflow fails, but the CI workflow runs correctly (but running the unit tests in windows-latest is taking a lot of time).

@ratfactor The cause of the problem of the forced termination was https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast. The error was confusing because there was no detailed error message about the reason for canceling the job....