From b950e503dbd24184c3f6566254eb50e3490e306e Mon Sep 17 00:00:00 2001 From: Jason Steving Date: Mon, 6 Dec 2021 02:32:25 -0800 Subject: [PATCH] ClaroSupport working efficiently! And NOW.....A REPL on RIJU! This is the final push towards implementing legitimate support for Claro in Riju! I've now figured out how to package up all of the Bazel generated build resources (jars) and the Bazel generated run script and have pieced everything together so that rebuilds and initial page loads are all as efficient as I can make them so far accounting for the intermediate step of compiling to Java. The general process is to package everything needed from Bazel in a tarball and then to dynamically insert a custom script to the Bazel generated run script in bazel-bin to rebuild and update the jar file for the latest modification to the file. This allows me to canibalize Bazel's logic for determining where all the proper "runfiles" a.k.a. jars are located in that tarball. With this approach I'm also able to trivially support the Claro REPL in Riju as well!!!!! This is the greatest unexpected surprise :D. --- langs/claro.yaml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/langs/claro.yaml b/langs/claro.yaml index 4aaeac3..4d9c068 100644 --- a/langs/claro.yaml +++ b/langs/claro.yaml @@ -100,4 +100,10 @@ run: | popd > /dev/null repl: | - java -jar claro_compiler_binary_deploy.jar --repl --silent \ No newline at end of file + java -jar claro_compiler_binary_deploy.jar --repl --silent + +input: | + print(123 * 234); + +skip: + - runrepl