Claude Code transcript

Now I can see the pattern. The parser at line 169 checks if a type keyword (INT_TYPE, etc.) is followed by FUNCTION or FUNC, but when INLINE appears between them (e.g., INT INLINE FUNCTION), it doesn't match and falls through to variable declaration parsing.

Let me look at the exact parser code around that area more carefully.

I have a clear understanding of the issue and the fix. The INLINE keyword between the return type and FUNCTION isn't recognized, so the parser falls through to variable declaration parsing. I need to:

1. Add INLINE as a keyword token in the lexer
2. Route INT INLINE FUNCTION ... to parseFuncDecl() in the parser
3. Skip INLINE in parseFuncDecl() before consuming FUNCTION

Let me also add tests.

The INLINE FUNCTION error from line 29 is gone — the remaining errors are from other unsupported features in bar.occ (variant protocol string; INT::[]BYTE, SHARED CHAN, etc.) which are separate issues. The fix is working correctly.

Now let me update TODO.md as recommended in the workflow:

All tests pass. Here's a summary of the changes:

Problem: INT INLINE FUNCTION seconds(VAL INT s) caused parse error expected :, got FUNCTION because the parser didn't recognize INLINE between the return type and FUNCTION.

Fix (3 files):

1. lexer/token.go — Added INLINE as a keyword token so it's recognized instead of being treated as an identifier.

2. parser/parser.go — Two changes:

3. parseStatement(): Added p.peekTokenIs(lexer.INLINE) to the condition that routes type keywords to parseFuncDecl() (line 169)

4. parseFuncDecl(): Added a check to skip the INLINE token if present before consuming the FUNCTION keyword

5. parser/parser_test.go — Added two new tests:

6. TestInlineFuncDecl — VALOF form with INT INLINE FUNCTION
7. TestInlineFuncDeclIS — IS form with INT INLINE FUNCTION

Documentation updated: TODO.md and CLAUDE.md both updated to reflect the new feature.

The INLINE modifier is purely an optimization hint and is ignored for transpilation — the function is parsed and generated exactly as if INLINE were absent, as agreed in the issue discussion.