Builder's Compiler

Compiler

PR: #685

Overview

Builder's compiler provide a ability to make user's coding experience better with following features:

Progress

1. Get code inlayhint, include unit and parameter.
2. Get code error(lint) list, to make sure the code quality.
3. Get cursor token, return it types,name,...

Pending

4. Get complete suggest list while user input.

Any stuff may have

1. Token's type, name, package, comment, function signature, ...
2. Error's type, position, content, parser, suggest(maybe some lint?)
3. To find how to suggest input.

Any stuff need form frontend

1. Code
2. Cursor position
3. ....

Problem

1. Where those data from?
2. Return's data struct.
3. ....

Solve way

1. WASM(to make sure frontend have the ability to run go lang)
2. AST parser.
3. Parse Tree?
4. Types info

TODO

• AST paser? | Inspect find?
• Types info getter(function signature, ...).
• Token struct
• Paser errors list
• Code complete suggest plan?
• WASM port
• List errors type and detail
• List token type & detail

From AST

1. Position
2. Name
4. ...

From types info

1. Funcition signature
2. Type
3. Position
4. ...

Other

Start by reviewing PR #685 and the unresolved TODO list, then define the data sources and return structures for AST, type information, errors, tokens, and completion. The issue names no files, tests, or entry points; done should be a decided scope and implementation plan for the compiler features and WASM port.