Refactor split and splice implementations.

Currently, the implementations of the split and splice operation are both
hidden behind the Bazel API implementation. This was sufficient to implement
splitting at the server and splicing at the client. In order to support the
other direction of splitting at the client and splicing at the server while
reusing their implementations, the code needs to be refactored. First, the
functionality of split and splice are explicitly exposed at the general
execution API interface and implemented in the sub APIs. Second, the
implementations of split and splice are factored into a separate utils class.

1 files changed, 0 insertions, 4 deletions

diff --git a/src/buildtool/execution_api/execution_service/cas_server.hpp b/src/buildtool/execution_api/execution_service/cas_server.hpp
index c9f7cff4..306c2833 100644
--- a/src/buildtool/execution_api/execution_service/cas_server.hpp
+++ b/src/buildtool/execution_api/execution_service/cas_server.hpp
@@ -147,10 +147,6 @@ class CASServiceImpl final
                                               bazel_re::Digest const& computed)
         const noexcept -> std::optional<std::string>;
 
-    [[nodiscard]] auto EnsureTreeInvariant(
-        std::string const& data,
-        std::string const& hash) const noexcept -> std::optional<std::string>;
-
     gsl::not_null<Storage const*> storage_ = &Storage::Instance();
     Logger logger_{"execution-service"};
 };