ess to be either through a known interface or by using
dynamic invocations. The original intent of <code>@proxy</code> (to implement a class
that isn't known statically, as documented at the end of this text),
is not supported by Dart 2.
To continue to perform dynamic invocations on an object,
it should be accessed through a reference of type <code>dynamic</code>.</p>
<p>The annotation <code>@proxy</code> marks a class as implementing members dynamically
through <code>noSuchMethod</code>.</p>
<p>The annotat