I was referring to the first example posted in the description of this JIRA issue by Peter.
I had not looked at your fix. So I'm not saying that certain things which compiled before work now, or vice versa, don't worry!
So if you fixed this so that we get a proper compilation error rather than an AsmClassGenerator error, then that's great.
That said, if we open a new JIRA issue for the consistency with passing a map as a possibly index, just like we use maps in method calls, then the fix for that new JIRA issue will certainly make you make some changes to what you committed, as the script in the description of this JIRA issue will become "compilable" (although it will throw some error at runtime because there's no getAt() like that defined on map.
So as you fixed this issue, please close it, that's fine, and I'll open a new issue for the consistency suggestions.
Does this sound okay?