Kevin Gibbons

> other than that it seems weird to have a variable be visible across multiple `{ ... }` That's the normal behavior of variables: a variable declared in some outer...

@ljharb The declaration _is_ outside both sets of curly braces. If that's the rule, it should be available in both.

Seems like something which should wait until the function decorators proposal, then? It makes sense to leave space for it in the API design, but if we think it's only...

That's not something in this API; it's a closed-over parameter in my example code.

I think there's some confusion here. `injectionKey` in my sample code _is not part of the API_. It is _purely_ a thing in the sample code. When I write `@inject('store')`,...

Yeah it would probably want a different name; `metadataKey` or something would be more obvious.

By "class" I intended syntactic `class` specifically, which are the only thing decorators be applied to. But now that you mention it I guess I could hypothetically see value in...

Yeah, I'd think that would be null (or undefined, I guess). From the perspective of a decorator author I think that would not cause any problems; the thing you would...

A compiler which emits JS can do whatever it wants; it doesn't need to depend on syntax in the language to provide functionality. For example, your snippet can be achieved...

> I'm not sure where you're getting a "shared string-based global namespace" from my example. Sorry, let me clarify: if all decorators from all libraries are contending over the string-named...