Scope-Based Code Autosuggestion With Object Property Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IDEs and code editors often fail to provide scope-based auto-suggestions that are semantically accurate, suggesting unnecessary code and failing to present desirable object elements and expressions, thus limiting coding efficiency and accuracy.

Innovation Solution

A system is developed that provides scope-based source code autosuggestion with object behavioral property detection, using a parser to identify constructs within the source code, a lookup module to match input characters with contextually relevant constructs, and an auto-completion module to suggest scope-matched constructs in real-time, while considering visibility scopes and updating suggestions dynamically.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If existing IDEs provide auto-suggestion features, then coding speed is improved, but the suggestions are not semantically accurate and suggest unnecessary code

Engineering Contradiction:
Improvecoding speedVSAvoidsemantic accuracy of suggestions
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system segments the codebase into scope regions with defined visibility boundaries. The autosuggestion engine queries only within the current scope region, dividing the large codebase into manageable semantic units. This segmentation enables precise contextual suggestions while maintaining high coding speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements scope-based visibility rules that give different parts of the codebase different accessibility properties. Objects and variables are suggested based on their scope visibility at the current insertion point, ensuring semantically accurate suggestions tailored to the local context rather than generic global suggestions.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If existing IDEs provide comprehensive auto-suggestions, then more code options are available, but desirable object elements and expressions are not presented

Engineering Contradiction:
Improvecode option availabilityVSAvoidrelevance of suggested constructs
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system uses the parser to continuously analyze the current code context and provides feedback to the autosuggestion engine. This feedback mechanism identifies the current scope region and filters suggestions to only include constructs visible within that scope, ensuring high relevance while maintaining comprehensive coverage of available options.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The parser pre-processes the source code to identify scope regions, visibility boundaries, and construct definitions before autosuggestion is needed. This preliminary action prepares the contextual information in advance, enabling the system to quickly present relevant object elements and expressions without sacrificing completeness.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If scope-based analysis is implemented, then suggestion accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvesuggestion accuracyVSAvoidsystem architecture complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system introduces a scope region data structure as an intermediary between the parser and the autosuggestion engine. This intermediary captures scope boundaries and visibility information in a structured format, simplifying the complexity by providing a clear interface for scope-based queries without requiring complex logic in the suggestion generation process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs scope analysis and region identification in advance during the parsing phase, storing the results in a data structure that the autosuggestion engine can efficiently query. This preliminary action separates the complex scope analysis from the suggestion generation, reducing overall system complexity while maintaining high suggestion accuracy.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260056713A1Scope-based source code autosuggestion with object behavioral property detection
Publication Date: 2026.02.26 ZOHO OFFICE SUITE
  • US20260056713A1 patent drawing
  • US20260056713A1 patent drawing
  • US20260056713A1 patent drawing

AI summary

A system providing scope-based source code autosuggestion, with object behavioral property detection and automated template generation is disclosed. Constructs are identified in source code in one or more files. Characters are input at a location. Constructs matching the characters and within the location scope, based on surrounding code structure, are placed in a list. The list of scope-matched constructs are output to the user in real-time, and the characters may be auto-completed responsive to a user selection. The constructs identified may be limited to those contextually relevant to current scope, such as within the same function, class, or namespace. Code templates may be located, adapted to the construct, and displayed for auto-completion. The user may select one of the list items for insertion into the source code. The scope-matched constructs are updated in real-time responsive to user input, dynamically refining the list.