alisha-1000 commented on issue #1096: URL: https://github.com/apache/mahout/issues/1096#issuecomment-3976830013
Thanks for raising this — I agree that hardcoding the CUDA-supported encodings in the error message can easily lead to drift as new encodings are introduced. I’d be happy to take this up. My plan is to centralize the CUDA-supported encoding list (e.g., via the encoding registry or a supports_cuda flag) and have validate_cuda_tensor_for_encoding derive the message dynamically from that source. This should keep the error messaging fully aligned with the implementation and avoid future maintenance overhead. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
