[Feature Request] An equivalent of parseString but only for imports/exports (NamespaceDirective).
#53498
Labels
area-dart-model
For issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.
8000
model-parser
Parser issues in the analyzer/CFE
P4
Comments
|
Fwiw, we do have lots of our own tools that only want to look at directives. So some improvement here would be appreciated for sure. We actually spend a large amount of time compiling web projects (with build_web_compilers) just in parsing directives. |
|
For me this is a P1 😁 Tools that depend on analysis need to be improved ASAP. |
|
Any update? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[ This is related to: Dart analyzer ]
When scanning for imports in the code, the current implementation requires fully parsing a Dart file. Since imports are only present at the beginning of the file, it would be very useful to have the ability to parse only the imports (stop parsing after the last import/export is detected).
This can significantly improve the response time of tools that need to analyze the import path or provide code suggestions.
Currently, the Dart Analyzer is experiencing increased response times due to its increased complexity. For medium to large projects, it's no longer "instantaneous".
I conducted some experiments using a simple
RegExpto extract the last import in the Dart code. Then, I split the file and passed only the top of the Dart file to theparseStringfunction. The performance was 3-4x times faster than analyzing the full file (I only want theNamespaceDirectivein the code in my case).The text was updated successfully, but these errors were encountered: