Fix visibility of impl fns getting dropped by the cube macro #212
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem The cube macro wasn't carrying over the visibility of impl fn items in its code generation for the _expand version of fns. While this doesn't cause issues for within-module references to those fns, it does cause compilation errors like
"__expand_{fn_name} is private"if you try to reference those fns from outside the module. See the PR's added test incrates/cubecl-core/tests/frontend/cube_impl.rsfor an example exercising this behavior.Proposed solution Add
vistoKernelFn, and output tokens for thatvisduring token generation. In most code paths,visis populated with the sourceImplItem's visibility. However, inLaunch's code path we setKernelFnto have pub visibility to match existing behavior.