Seeing obfuscated names on the call stack

[vsmenon]

See the main$ instead of main.

This is with the latest beta:

> flutter --version
Flutter 1.26.0-17.5.pre • channel beta • https://github.com/flutter/flutter.git
Framework • revision 1fe38dcb5f (5 days ago) • 2021-02-10 16:25:47 -0800
Engine • revision d4453f6018
Tools • Dart 2.12.0 (build 2.12.0-259.9.beta)

[nshahan]

In general the names that end with the suffix $, $1, $2, ... $n are given that name when the original conflicts with another name in the Javascript scope. Our longterm solution is to emit a full mapping of the renames in every scope so we can show the Dart name in the tools and find the correct JS name when an evaluation uses the Dart name.

This specific example of obfuscated names looks like a side effect of how DDC represents async methods as two nested functions where the inner method gets renamed with the $ suffix to avoid shadowing the outer method. See dart-lang/sdk#44374 but the solution for VSCode (I think what I see in the screenshot) might be different than what we eventually do for Dart/Flutter Dev Tools.

@DanTup How does the VSCode extension decide if it should show or hide a stack frame for a web project?

[DanTup]

VS Code currently shows all frames (preferring the asyncCausalFrames), although there's some tweaking for things like the async marker and or to flag package/SDK frames (so they can be "collapsed" and greyed by VS Code).

No frames are ever outright excluded/skipped. I think it'd be possible to do if there was a need, although it would probably be better done in the service so it's just transparent to all editors to avoid them having to rewrite the indexes when calling things like evaluateInFrame.