bug(developer): kmc-kmn kmw compiler generates an incorrect offset for nul ... > index(store,n) when in v10+ mode

[mcdurdin]

store(&version) '10.0'
store(&TARGETS) 'any'

begin Unicode > use(main)

store(cons) 'mnpqrstv'

group(main) using keys

nul any(cons) + 'e' > '5' index(cons,2)

With this keyboard in Keyman Core 15.0 or later (e.g. debugger, Keyman for Windows), try typing: te

• The output should be 5t.
• For KeymanWeb v9 mode, the output is: 5t (correct).

Bugs:

• For KeymanWeb v10 mode, the output is: 5.

This issue is present in Keyman Core 15.0 and later versions. I have not tested earlier versions.

Note that using index(cons,1) gives a compiler error which makes total sense:

test_13276.kmn (20): Error: 4032 An index() in the output does not have a corresponding any() statement

I have tested the same pattern with if() and it works correctly in Keyman Core, KeymanWeb v9 mode, and KeymanWeb v10 mode.

Related issues:

• bug(developer): context(n) counts the nul statement as a character in Web & android #13276