[core] Split giant ray core C++ targets into small ones(stats) #50588
Labels
core
Issues that should be addressed in Ray Core
dependencies
Pull requests that update a dependency file
enhancement
Request for new feature and/or capability
As of now, ray core uses bazel as build system, which encourages small targets.
Ray core is not following the best practice, which bundles all related files into several giant targets. For more information, check out the master issue
Part of #50586
The text was updated successfully, but these errors were encountered: