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

Compilation database should be generated earlier #134

Open
TheRustifyer opened this issue Aug 25, 2024 · 0 comments
Open

Compilation database should be generated earlier #134

TheRustifyer opened this issue Aug 25, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request refactor

Comments

@TheRustifyer
Copy link
Member

Refactor

The compilation_database (compile_commands.json) is generated (if necessary) at the very end of the process.

Working with Zero I faced several times where I moved around files, and my neovim setup was unaware of the changes, so it was a total mess of errors and warnings raised by the LSP client.

It would be fine that the compilation database was (re)generated after the generate_commands procedure, and even further, to have a dedicated CLI arg that stands for such purpose, which implies to (re)generate the commands and (re)generate the compilation database, so users can update such entity without running full processes.

@TheRustifyer TheRustifyer added enhancement New feature or request refactor labels Aug 25, 2024
@TheRustifyer TheRustifyer self-assigned this Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactor
Projects
None yet
Development

No branches or pull requests

1 participant