Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An idea for future updates to this repo #17

Open
The-Lord-of-Owls opened this issue Aug 24, 2023 · 2 comments
Open

An idea for future updates to this repo #17

The-Lord-of-Owls opened this issue Aug 24, 2023 · 2 comments

Comments

@The-Lord-of-Owls
Copy link

Assuming you ever come back to working on this, you should try and make a VS Code extension that will scan through addons while they are being developed to find optimization issues in real time.

@ExtReMLapin
Copy link
Owner

it's a runtime tool, not a static code analyzer, it allows much more robusts ways to know if a function is ran in a hook/specific context

@The-Lord-of-Owls
Copy link
Author

Late reply but fair enough, I eventually found a separate tool that kinda achieved what I was suggesting back then, The WilliamVenner/vscode-glua-enhanced repo has been a great help before loading gmod and BadCoderz is a great help after loading into gmod.

I regularly use both, aswell as Dbugr and fProfiler before finishing a release. Maybe it would worth adding a mention to the vscode-glua-enhanced extension for others who might not already be using it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants