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

Expose per-compilation-unit cfg sets in scarb metadata #1085

Merged

Conversation

szymmis
Copy link
Contributor

@szymmis szymmis commented Jan 25, 2024

Depends on #1084
Resolves #1076

@szymmis szymmis linked an issue Jan 25, 2024 that may be closed by this pull request
@maciektr
Copy link
Contributor

maciektr commented Jan 30, 2024

I feel like this ops/metadata and db helper functions are too smart. Why not store the cfg set on CompilationUnitComponent where applicable and keep all cfg resolution in the compilation unit generation step (similar to what has been done in CompilationUnit)?

@szymmis
Copy link
Contributor Author

szymmis commented Jan 30, 2024

Makes sense @maciektr, I'll look into it

@szymmis szymmis force-pushed the szymmis/per-crate-cfg-set-metadata branch from f3d8cce to 30c8c38 Compare February 1, 2024 11:59
@szymmis szymmis force-pushed the szymmis/deps-test-compilation branch from bd58c5e to 9298c13 Compare February 1, 2024 12:00
@szymmis szymmis force-pushed the szymmis/per-crate-cfg-set-metadata branch from 30c8c38 to 2687248 Compare February 1, 2024 12:01
@szymmis szymmis merged commit 2687248 into szymmis/deps-test-compilation Feb 1, 2024
4 checks passed
@szymmis szymmis deleted the szymmis/per-crate-cfg-set-metadata branch February 1, 2024 12:20
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

Successfully merging this pull request may close these issues.

Expose per-crate cfg sets in scarb metadata
2 participants