This issue entails the implementation / updating of all types to match the LSP spec rather than ZLS use-cases only.

Base Protocol

• Request Message
• Response Message
• Notification Message
• $/cancelRequest
• $/progress

Basic Structures

• URI
• Regular Expression
• Text Documents
• Position
• Range
• Location
• Location Link
• Diagnostic
• Command
• Text Edit
• Text Document Edit
• File Resource Changes
• Workspace Edit
• Text Document Identifier
• Text Document Item
• Versioned Text Document Identifier
• Text Document Position Params
• Document Filter
• Static Registration Options
• Text Document Registration Options
• Markup Content
• Work Done Progress
• Client Initiated Progress
• Server Initiated Progress
• Partial Results
• Partial Result Params
• Trace Value

General Messages ($/)

• initialize
• initialized
• shutdown
• exit
• logTrace
• setTrace

Window (window/)

• showMessage
• showMessageRequest
• showDocument
• logMessage
• progress/create
• progress/cancel

Telemetry (telemetry/)

• event

Client (client/)

• registerCapability
• unregisterCapability

Workspace (workspace/)

• workspaceFolders
• didChangeWorkspaceFolders
• didChangeConfiguration
• configuration
• didChangeWatchedFiles
• symbol
• executeCommand
• applyEdit
• File Operations Events

Text Documents (textDocument/)

• General Capabilities
• didOpen
• didChange
• willSave
• willSaveWaitUntil
• didSave
• didClose
• publishDiagnostics

Language Features (textDocument/)

• completion + resolve
• hover
• signatureHelp
• declaration
• definition
• typeDefinition
• implementation
• references
• documentHighlight
• documentSymbol
• codeAction + resolve
• codeLens + resolve + refresh
• documentLink + resolve
• documentColor
• colorPresentation
• formatting
• rangeFormatting
• onTypeFormatting
• rename
• prepareRename
• foldingRange
• selectionRange
• prepareCallHierarchy
• Call Hierarchy incoming + outgoing
• Semantic Tokens
• linkedEditingRange
• moniker

@slimsag 😭😭😭

Responses need to be deserializable so LSP clients can be implemented with this library.

Depends on a subset of #2.

Some request results have slices, like textDocument/hover's MarkupContent.

When using lsp.Connection, the signature is

pub fn @"textDocument/hover"(conn: *Connection, id: lsp.types.RequestId, params: lsp.types.HoverParams) !lsp.types.Hover

If I set up an arena allocator inside the implementation, the memory returned becomes invalid. Is there a simple way to do this without leaking memory?