Open ghostbutter-games opened 7 months ago
I can confirm I have had these problems too.
Instead of creating another autocomplete feature request, I'll just add it here:
Stuff from preload is always in the global scope. But I have to explicitly import it with #import "Preload"
to get the autocompletion for things like Type_Info_Struct
and friends. And explicitly importing Preload is quite discouraged by the compiler!
Instead of creating another autocomplete feature request, I'll just add it here:
Stuff from preload is always in the global scope. But I have to explicitly import it with
#import "Preload"
to get the autocompletion for things likeType_Info_Struct
and friends. And explicitly importing Preload is quite discouraged by the compiler!
Jails currenty does not include Preload
or Runtime_Support
by default in its analyzer. I´ve already start to work on this.
Hi, first of all a big thank you for building this, I very much appreciate the effort and usability that's already there!
I am running into a couple of issues when using VSCode and the LSP with regards to Auto-complete:
Structs
.{}
breaks the auto-completion. Reproduction:my_struct : My_Struct; // For comparison, this works with auto-complete my_struct.my_value = 5;
#import
auto-completeEDIT: It seems like the newest Jai version (0.1.086) fixed the auto-complete of the module I was using again, thankfully. However, I have one quality of life issue:
When importing my Raylib module via
rl :: #import "raylib";
and then usingrl.
, the auto-completion list includes everything, including other module's namespaces, like e.g. theBasic
module, etc.It would be great if this could be fixed somehow, as
rl.log
does not make any sense / does not exist, but is still suggested as a valid auto-completion.