Angle Bracket Invocation allows implicit this with paths

[rwjblue]

Per the angle bracket invocation RFC using a path for invocation should not use “implicit this” fallback.

Specifically, the following should not render a curried component at this.foo.bar:

<foo.bar />

[rwjblue]

The RFC's reasoning seemed to be about avoiding costly this.div type lookups in the non-path case (e.g. <div></div>), but it isn't completely clear to me that we also want to require this. for paths.

Specifically, I think that it may make more sense to limit the explicit this. requirement to cases that are not paths already (which satisfies the <div></div> case I mentioned above), and leave completely removing the implicit this to emberjs/rfcs#308.

@chancancode - What do you think?

[rwjblue]

Chatted with @chancancode, the RFC's language was intentional. glimmerjs/glimmer-vm#827 should fix this for us once released.

[pixelhandler]

@rwjblue closing for now, that should have been released by now, correct?

glimmerjs/glimmer-vm#827

[rwjblue]

Ya, perfect