What is the current progress of the major adjustment mentioned in this place?

47 views
Skip to first unread message

白沙

unread,
Dec 10, 2022, 3:29:12 AM12/10/22
to Dart Analyzer Discussion

74C373A7-B5FD-4F00-AC06-7CEB1CF7028E.png

Samuel Rawlins

unread,
Dec 10, 2022, 12:59:19 PM12/10/22
to analyzer...@dartlang.org
> What is the current progress of the major adjustment mentioned in this place?

I think little to no progress.

On Sat, Dec 10, 2022 at 12:29 AM 白沙 <tenu...@gmail.com> wrote:

74C373A7-B5FD-4F00-AC06-7CEB1CF7028E.png

--
You received this message because you are subscribed to the Google Groups "Dart Analyzer Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to analyzer-discu...@dartlang.org.
To view this discussion on the web visit https://groups.google.com/a/dartlang.org/d/msgid/analyzer-discuss/e1f9e99c-9204-4654-a37f-14fed0556ce7n%40dartlang.org.

Brian Wilkerson

unread,
Dec 12, 2022, 12:22:04 PM12/12/22
to analyzer...@dartlang.org
I actually think we've made significant progress. The work isn't completely done, but if a client of the analyzer package sticks to the APIs that are not in `src` I think they're relatively safe.

If you find APIs that aren't public that you need, please let us know so that we can consider whether to make it part of the public API.

Samuel Rawlins

unread,
Dec 12, 2022, 2:44:28 PM12/12/22
to analyzer...@dartlang.org
On Mon, Dec 12, 2022 at 9:22 AM 'Brian Wilkerson' via Dart Analyzer Discussion <analyzer...@dartlang.org> wrote:
I actually think we've made significant progress. The work isn't completely done, but if a client of the analyzer package sticks to the APIs that are not in `src` I think they're relatively safe.

Ah that's good! I spoke too soon. The big ones I've always wanted are Navigator (exposed in other public API) and InheritanceManager3, which might not be exposed by any public API. I just use that one sometimes in linter rules. 

If you find APIs that aren't public that you need, please let us know so that we can consider whether to make it part of the public API.

On Sat, Dec 10, 2022 at 9:59 AM 'Samuel Rawlins' via Dart Analyzer Discussion <analyzer...@dartlang.org> wrote:
> What is the current progress of the major adjustment mentioned in this place?

I think little to no progress.

On Sat, Dec 10, 2022 at 12:29 AM 白沙 <tenu...@gmail.com> wrote:

74C373A7-B5FD-4F00-AC06-7CEB1CF7028E.png

--
You received this message because you are subscribed to the Google Groups "Dart Analyzer Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to analyzer-discu...@dartlang.org.
To view this discussion on the web visit https://groups.google.com/a/dartlang.org/d/msgid/analyzer-discuss/e1f9e99c-9204-4654-a37f-14fed0556ce7n%40dartlang.org.

--
You received this message because you are subscribed to the Google Groups "Dart Analyzer Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to analyzer-discu...@dartlang.org.
To view this discussion on the web visit https://groups.google.com/a/dartlang.org/d/msgid/analyzer-discuss/CACshfx2x2cWJ91wo_irQ5h%3D0qcAogte_gikn%3DBwfFOfoJWmieQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Dart Analyzer Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to analyzer-discu...@dartlang.org.

白沙

unread,
Dec 13, 2022, 2:51:31 AM12/13/22
to Dart Analyzer Discussion, sraw...@google.com
Wow, this news is so surprising, since the last year or so, I dare not adjust the related business, worrying about facing great changes in the future, thank you for this timely reply.

Brian Wilkerson

unread,
Dec 13, 2022, 11:21:06 AM12/13/22
to analyzer...@dartlang.org, sraw...@google.com
You're welcome.

I will point out, in case it impacts your decision, that the analyzer package is still always evolving and we regularly publish breaking change releases. This has less to do with moving APIs from public to private (or the inverse) as it does with the need to support new language features. I don't expect that need to change anytime soon, so if it's too expensive to deal with breaking changes you might still want to be cautious about using the analyzer package.

Reply all
Reply to author
Forward
0 new messages