reactor(cust_raw): Generate bindings for cuda types and restructure cust_raw's crates#201
reactor(cust_raw): Generate bindings for cuda types and restructure cust_raw's crates#201jorge-ortega wants to merge 1 commit intoRust-GPU:mainfrom
cust_raw's crates#201Conversation
|
The |
|
The convention tends to only apply to the top-level crate name, not the crates inside of it. The raw in cust_raw kinda conveys what sys is supposed to (there be bindings in here), so if you consider that it comes off a bit redundant: The important thing is users understand that the crate as a whole only contains bindings before they even add it as a dependency, which should make them gravitate to the higher-level crates. Still hoping on hearing back from the owner of cuda-sys in #182. |
Yeah, if we do can get the cuda-sys crate, I agree that we can drop the "-sys" suffix. |
|
I reached out to them over email. |
…cust_raw`'s crates - Allow list files instead of types/var/functions. - Split out type headers from runtime/cublas to their own crates.
608a845 to
3ee02bb
Compare
|
I'm splitting out the module renames from this change and will open a separate PR for that. This should now contain just the restructuring and new type bindings. Clippy seems to be building the examples and is now failing during LTO. I don't repro this on windows or in ubuntu24 devcontainer. |
This restructures cust_raw to the following:
This is a precursor to adding other CUDA library bindings, like nvJPEG and cudaFFT.