NullVoxPopuli

do you have a repo I can try to reproduce this issue in? I have an old glint@unstable here, and this does what I expect: 

Can you add a screenshot of what the syntax highlighting looked like before? Thanks!

> It might be a challenge, in a class-backed component where you need to access a member of the class, in which this will be required. arrow functions would use...

> I thought it was supposed to be @bound or something like that... decorators would first need to be implemented, and it seems browsers are nearly there. Additionally, all build...

There is _certainly_ some nuance to methods in classes if you want the _most performance_ possible. Fwiw, I'm also ok with blocking this on waiting on the Glimmer VM to...

> I think you should add to the downsides section that this change makes existing online content incompatible with the docs. This is not true. `@action` isn't going away. >...

> I gave the arrow syntax a try on a willTransition that was working with @action and the arrow syntax doesn't seem to work in that scenario. This tells me...

> We could discuss whether we should also deprecate @action. _for now_, I don't think we should deprecate anything. A future RFC could deprecate the non-bind _behaviors of `@action`_, however

> @action should be recommended explicitly for situations like inheritance and the one or two others that have been called out. I’d like to see that mentioned in the RFC...

> It's tedious to maintain code that has arrow functions everywhere. more than action? if so, I don't agree. or more than regular methods that should have worked the whole...