You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, upon stack, scope, or object requests from IDEs, dwds does some heuristic processing of JavaScript frames and variables in current scope to make them appear as coming from dart. While that approach work in many cases due to JavaScript code produced by DDC being very close to dart, there are some corner cases where the heuristics fail. This also imposes limitations on changes in DDC, as they may break the heuristics.
We need a more reliable approach where the debugger can use compiler's symbol and type information, as well as mapping from JavaScript to dart symbol and type (via locations?) in order to have dart-oriented internal representation of stacks, scopes, and objects.
Currently, upon stack, scope, or object requests from IDEs, dwds does some heuristic processing of JavaScript frames and variables in current scope to make them appear as coming from dart. While that approach work in many cases due to JavaScript code produced by DDC being very close to dart, there are some corner cases where the heuristics fail. This also imposes limitations on changes in DDC, as they may break the heuristics.
We need a more reliable approach where the debugger can use compiler's symbol and type information, as well as mapping from JavaScript to dart symbol and type (via locations?) in order to have dart-oriented internal representation of stacks, scopes, and objects.
Related issues
dart-lang/sdk#40776
The text was updated successfully, but these errors were encountered: