ryuukk

There seems to be something very wrong with sublime LSP Here a different server: ols https://github.com/DanielGavin/ols/ Using sublime odin: https://github.com/odin-lang/sublime-odin ``` >>> view.settings().get("auto_complete_triggers") [{'characters': '#"/:', 'selector': 'meta.tag, source - comment...

> Could be the same issue. > > If you type `rt.`, then cancel the completion popup and then type `e` then it works? No luck, it still doesn't show...

Some logging information when it builds the CompletionItem, i put some print in completion.py file trigger: ``erro(fmt: string, args: ..any, location := caller_location)`` annotation: ``rt.erro: proc(fmt: string, args: ..any, location...

Same problem if the server doesn't send the ``detail`` If it works with vscode, it should work with sublime How do i debug this further?

 # On the left ``rt.er`` : sublime text show no completion, despite the item being on the json log: ``` trigger: erro(fmt: string, args: ..any, location := caller_location) annotation:...

Even if i change the symbol's name, it's always the same: 2 first character doesn't show the completiton, it always starts at the 3rd character i type, definitely a bug...

Can someone review this please?

To help understand what this PR does: For cases where one uses -betterC or uses a custom runtime, it makes it possible to still use debugging APIs like `backtrace` Example...

It would be nice to run a benchmark by compiling s huge project, to see the benefits

I fixed the code style, and i added 2 tests, 1 runnable, and 1 fail-compilation Questions: - I need it to build a static lib, is the script i added...