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

Make hot reloading work #1968

Open
lerno opened this issue Feb 14, 2025 · 2 comments
Open

Make hot reloading work #1968

lerno opened this issue Feb 14, 2025 · 2 comments

Comments

@lerno
Copy link
Collaborator

lerno commented Feb 14, 2025

A problem with hot reloading is that the dynamic lookup tables will point to the wrong thing.

This could be solved by having a way to locate them and repatch them.

@alexveden
Copy link
Contributor

Also, it would be nice to have a simple caching of full stdlib object files, they got rebuilt every time I run c3c test/run/etc. I think it takes a major part of compilation time.

@alexveden
Copy link
Contributor

Please also consider another case of hot reloading - LSP syntax/error checks. It would be great to have kinda compilation c3c server, which holds parsed std lib and maybe a project files in memory. So the LSP server could send changes to a c3c server for syntax checks via stdin, and get results via stdout.

Currently, c3c run parsing on full stdlib and project at each run.

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