-
Notifications
You must be signed in to change notification settings - Fork 434
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 data
runtime-only to align with ecosystem norms
#2977
Comments
I think this makes sense to do - it was a mistake that we used Ideally we should introduce a flag to control this behaviour to make migration easier. Introduce the flag (I don't really mind what default we use), and delete the flag a release or two later when people have had an opportunity to migrate. Happy to review a PR doing this! |
I can send a PR but I may not get to it for a few weeks. If anyone else is motivated in the meantime, go for it |
In the current rules_rust rules, the
data
attribute is available both at compile time and at runtime whereas thecompile_data
is just available at runtime. There is no attribute that describes runtime-only dependencies. This is unfortunate; changing runtime dependencies shouldn't force a recompilation and relinking of an executable.In order to align with the rest of the bazel ecosystem, we should change
data
to not be available at compile time. This will be a breaking change, but it's worth it.The text was updated successfully, but these errors were encountered: