3pacccccc commented on PR #25928: URL: https://github.com/apache/pulsar/pull/25928#issuecomment-4620390711
> From a previous conversation with Gemini: > > It’s a common quirk that can make AI-generated code look a bit "clunky" compared to how a human would write it. While you might prefer a clean `import` statement at the top, AI agents often default to Fully Qualified Class Names (FQCN) for several practical and technical reasons. > > Here is why your AI "coworker" is being so verbose: > > ### 1. Avoiding Naming Collisions > AI models are trained on massive datasets where multiple libraries might have classes with the same name. For example, there are many different `Configuration`, `Context`, or `Action` classes across various Java frameworks. > > * By using the FQCN (like `org.apache.pulsar.common.policies.data.AuthAction`), the AI ensures the code is unambiguous. > * It eliminates the risk of the compiler getting confused if two imported packages contain the same class name. > > ### 2. Contextual Independence > When an AI generates a snippet of code, it often treats that block as a standalone unit. > > * The "Headless" Problem: Often, the AI provides the logic (the method body) without generating the entire file structure (package declaration and imports). > * By using the full path, the code becomes "plug-and-play." You can paste it into an existing file, and it will work immediately without you having to manually resolve imports or scroll to the top of your IDE. > > ### 3. Training Data Bias > A significant portion of AI training data comes from: > > * Stack Overflow snippets: Where users often use FQCNs to show exactly which library they are using. > * Machine-generated code/Protobufs: Auto-generated Java code (like that produced by gRPC or Thrift) frequently uses full paths to avoid errors, and the AI mirrors this pattern. > > ### 4. Deterministic Reliability > In the "mind" of an LLM, being explicit is safer than being implicit. If it writes an import statement at the top but then forgets to use it, or uses a different version in the code, the code fails. Using the full name directly at the call site is a "fail-safe" way to ensure the code compiles on the first try. thanks for sharing, It's good to know that -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
