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

Dynamic loading of dylibs in proc macro server #145

Open
piotmag769 opened this issue Jan 7, 2025 · 0 comments
Open

Dynamic loading of dylibs in proc macro server #145

piotmag769 opened this issue Jan 7, 2025 · 0 comments

Comments

@piotmag769
Copy link
Contributor

Currently the proc macro server only starts in a current directory, resolves the workspace and loads needed proc macros from all compilation units (the set of proc macros is fixed after that). The problem is that when we open other a package from other workspace that requires additional proc macros, we won't be able to resolve some macros in that package.

The proposed solution is to add a possibility to send a request to proc macro server that will make the server compile and load the proc macro. The request should contain a path with path to Scarb.toml of the proc macro - we should obtain the path from scarb metadata when we first enter a workspace.

@github-project-automation github-project-automation bot moved this to Triage in CairoLS Jan 7, 2025
@piotmag769 piotmag769 moved this from Triage to Backlog in CairoLS Jan 7, 2025
@piotmag769 piotmag769 added this to the Proc macros support milestone Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant