Erik Ernst

I think `.name ...` could work. This would allow the dot shorthand to remain a term where we're just omitting the name of the declaration whose static namespace we are...

Note that https://github.com/dart-lang/language/issues/4457 has a discussion which may seem related. However, I don't think there is much of an overlap.

Right, this is an attempt to explore the language design space for minimal static meta-programming features. A plain identifier substitution mechanism will only help in cases where we need to...

> 1. About: >> In order to avoid surprising effects, it is a compile-time error if an instantiation yields a declaration where an occurrence of an identifier is bound differently...

@rrousselGit wrote: > I guess the goal is similar to `flutter_hooks` then? Name parameterization and `flutter_hooks` are of course completely different things, but you could say that there are some...

@lrhn wrote: > I think I'd prefer to not allow a templated name to occur freely in the template. It does take a couple of steps to determine what this...

> This looks related to #4138. Right—one thing that comes to mind is that the name abstraction which is proposed here could be used to obtain a variant of the...

The syntax may seem magical, but I think it's mainly a specialist's job to write those name-parameterized declarations, and most Dart developers probably won't ever see them (but they might...

The actual syntax of any mechanism is always the topic of long debates. Expressing any given mechanism in a way that makes sense is definitely a goal for all members...

For the call-if-not-null case you can use an existing mechanism, the `call` method: ```dart class A { void Function() bar() => null; } main() { var foo = A(); //...