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

Replace Gluecodium cache mechanism with an external solution #904

Open
DanielKamkha opened this issue May 18, 2021 · 0 comments
Open

Replace Gluecodium cache mechanism with an external solution #904

DanielKamkha opened this issue May 18, 2021 · 0 comments
Labels
good-first-issue Good first issue for starting with the project

Comments

@DanielKamkha
Copy link
Contributor

Currently Gluecodium provides a built-in caching mechanism for generated files. The only use case where this mechanism is needed is preserving time stamps when files are re-generated in place, so that CMake could properly recognize these files as "not changed" if the file contents are the same.

This mechanism is hard to test, prone to corner-case errors, and is very unsafe in concurrency scenarios (both inside a single Gluecodium run and with several parallel Gluecodium instances). The proposal is to replace this mechanism with something external to Gluecodium itself. It can be, for example, a part of the CMake tool-chain as it is only needed for CMake usages anyway.

@DanielKamkha DanielKamkha added the good-first-issue Good first issue for starting with the project label May 18, 2021
@DanielKamkha DanielKamkha removed the good-first-issue Good first issue for starting with the project label May 27, 2021
@DanielKamkha DanielKamkha added the good-first-issue Good first issue for starting with the project label Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-first-issue Good first issue for starting with the project
Projects
None yet
Development

No branches or pull requests

1 participant