I’ve passed the stage #EY7 Scanning: Identifiers
But there is an error in the test workflow of this step. On the first hand, I think it’s a very weird choice to allow number in identifiers but, ok. The problem is that in this test, the workflow expects a token NUMBER 6 6.0 instead of an IDENTIFIER 6az null. This is not coherent with the expectation of other tests.
remote: [tester::#EY7] [test-2] Running test case: 2
remote: [tester::#EY7] [test-2] Writing contents to ./test.lox:
remote: [tester::#EY7] [test-2.lox] _123world_ foo f00 baz 6az
remote: [tester::#EY7] [test-2] $ ./your_program.sh tokenize test.lox
remote: [your_program] IDENTIFIER _123world_ null
remote: [your_program] IDENTIFIER foo null
remote: [your_program] IDENTIFIER f00 null
remote: [your_program] IDENTIFIER baz null
remote: [your_program] IDENTIFIER 6az null
remote: [your_program] EOF null
remote: [tester::#EY7] [test-2] ✓ IDENTIFIER _123world_ null
remote: [tester::#EY7] [test-2] ✓ IDENTIFIER foo null
remote: [tester::#EY7] [test-2] ✓ IDENTIFIER f00 null
remote: [tester::#EY7] [test-2] ✓ IDENTIFIER baz null
remote: [tester::#EY7] [test-2] 𐄂 IDENTIFIER 6az null
remote: [tester::#EY7] [test-2] Expected line #5 on stdout to be "NUMBER 6 6.0", got "IDENTIFIER 6az null"
remote: [tester::#EY7] [test-2] Test failed