You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solvers may wish to develop RISC-V solutions and/or translations locally. It isn't immediately obvious how to do so, since it differs from the native architecture of most consumer devices at the time of writing. At least it would be nice to mention that one does not need to purchase their own RISC-V SoC and load Linux on it in order to reproduce the Codewars environment locally ;-)
We could simply mention that Codewars uses ghcr.io/codewars/riscv for the execution environment and have the solver figure out the rest, but since it outputs Codewars output format which isn't very human-friendly, perhaps we should guide users on setting up a similar environment using the text reporter instead which gives human-friendly output, e.g. docker.io/donaldsebleung/cgreen
The text was updated successfully, but these errors were encountered:
but since it outputs Codewars output format which isn't very human-friendly, perhaps we should guide users on setting up a similar environment using the text reporter instead which gives human-friendly output
I think we can change the main to use human-friendly output based on an environment variable or a flag. Then change bin/run to support it.
Depends: #438
Solvers may wish to develop RISC-V solutions and/or translations locally. It isn't immediately obvious how to do so, since it differs from the native architecture of most consumer devices at the time of writing. At least it would be nice to mention that one does not need to purchase their own RISC-V SoC and load Linux on it in order to reproduce the Codewars environment locally ;-)
We could simply mention that Codewars uses
ghcr.io/codewars/riscv
for the execution environment and have the solver figure out the rest, but since it outputs Codewars output format which isn't very human-friendly, perhaps we should guide users on setting up a similar environment using the text reporter instead which gives human-friendly output, e.g.docker.io/donaldsebleung/cgreen
The text was updated successfully, but these errors were encountered: