Devon Carew

I'm coming into this conversation a little late, but the idea of using the `@pragma` annotation appeals to me. ```dart @pragma('dartdoc:import', 'package:flutter/material.dart') import 'dart:convert'; import 'dart:io'; import 'package:path/path.dart' as p;...

For a flavor of how `pragma`'s being used now, here are the unique uses in the sdk repo: ``` @pragma('dart2js:${annotation.name}') @pragma('dart2js:${other.name}') @pragma('dart2js:...') @pragma('dart2js:') @pragma('dart2js:as:check') @pragma('dart2js:as:trust') @pragma('dart2js:assumeDynamic') @pragma('dart2js:disable-inlining') @pragma('dart2js:disableFinal') @pragma('dart2js:downcast:check') @pragma('dart2js:downcast:trust')...

cc @scheglov

Hi - thanks for the PR. FYI that the source-of-truth for this package has moved to our dart-lang/labs monorepo; https://github.com/dart-lang/labs/tree/main/pkgs/native_synchronization. I'll close this PR, but feel free to re-create it...

Similarly to the previous comment, for transferred issues (like https://github.com/dart-lang/sdk/issues/56072), we should at least feed in the first and last comment if not all the comments. We may also consider...

We should auto-close `Analyzer Feedback from IntelliJ` issues; these almost universally do not contain information (are not customized over the default template that just sends version info).

See https://github.com/dart-lang/ecosystem/pull/274 for a few of the discussed improvements.

When an issue comment contains an image, we should pass that image into the gemini API (along with the issue comment's text).

Yeah, I agree that that summary is off; you were asking for an analyzer code assist and it summarized it as a language enhancement request. I don't know if that...

> Maybe a way to ask the bot for a review? Than you could have a little more context into the new review Do you mean to interact with the...