Code-assisted use cases: 1. New code. Esp boilerplate, templated sections, default implementations. 2. Existing code, altering purpose. 3. Existing code, sam

Code-assisted use cases: 1. New code. Esp boilerplate, templated sections, default implementations. 2. Existing code, altering purpose. 3. Existing code, same purpose but refactoring. For step 1, full-line completion seems like a halfway step. If the expanded result can usually be expressed with something more terse, why not go 100% and rely on a language that primarily uses terse version? Guess I'm waiting for the magical AI-universo-scripto language where only the bare minimum is typed by a human, and hovering (or IDE view mode) reveals details or full description. Or perhaps something more declarative: provide the terse goal, check the execution plan to make sure the full implementation fits or decide between competing implementations for same goal. For step 2, full-line completion is great because the surrounding code is left intact (and in fact is needed for reasonable AI suggestions). For step 3, I could see full-line completion being of use, but more limited since full-block or full-section completion might be more appropriate.