Solutions Workspace (Revised) about coctus HOT 5 OPEN

Storing the solutions is a good idea, but I think creating a git repository for each is wasteful and it would also add a dependency on git.

The clash solutions command should probably just print the paths to each solution on their own line – the user could then use fzf to pick one if they wish (but they could also easily use them in any other way):

$EDITOR $(clash solutions | fzf)

from coctus.

One issue I see with generating solutions automatically from clash run is that if you run for example

clash run --command "echo 42"

then there is not any sol.py file to save (and even the language is not clear). It would have to be something more like this to get all the necessary information:

clash save --build-command [BUILD_COMMAND] --command [RUN_COMMAND] --code-file [FILE] --language [LANGUAGE]

from coctus.

Revised this suggestion, any feedback would be appreciated.

from coctus.

I think the proposed clash solve command seems reasonable, and making clash run check current directory for puzzle.json is probably acceptable overhead. I don't understand the clash commit command though, wouldn't the solution already be saved in $soldir? And why would someone want a copy instead of just modifying the current one?

from coctus.

I think the proposed clash solve command seems reasonable, and making clash run check current directory for puzzle.json is probably acceptable overhead.

👍

I don't understand the clash commit command though, wouldn't the solution already be saved in $soldir? And why would someone want a copy instead of just modifying the current one?

The purpose of clash commit in my head is to let you iterate quickly. Say you are trying to golf a clash, and you feel like you can no longer remove chars from this type of solution, you just coctus commit ruby_eval_60 and then try a different implementation.

The idea being that it's a quick and easy way to save a working solution if you need to go back to it.

I think my explanation in the first post was a little strange, it's more just making a copy and saving it while you can continue to work on the current solution. Think git branch.

from coctus.