Approved.

.

Approved. Thanks!

My assumption is that the two instructions won't be in the critical dependency chain, so they can be placed anywhere and executed "for free" in more advanced microarchitectures. IDK how much I should worry about this with diversity of RISC-V hardware. And I guess if they are before the branch, there's no need to wait for the branch condition to be ready to retire them.

To save in case of an in-order single-issue CPU? I'm not sure how many of those there are with vector extension support.

Approved

"And also it's a great chance for warriors to start learning V while seeing its usage with some explanation."
Good point, I agree.

I'm not sure that I understand what you mean. The "V" in "RISC-V" stands for 5, not "Vector", the vector extension is entirely optional and most RISC-V CPUs don't implement it.

Sure, you can follow the tradition. I was just copying what most other RISC-V kata are doing, which is void return type and (src, dst) argument order.

The main change was the reference solution. Your solution uses the vector extension, which is not how most people will solve this. Also not many people will understand how your solution works, despite the descriptive comments.

A typo.... obviously

...aaaaand what exactly is cosnt?

Approved, with a follow-up fork for unification with C and NASM translations.

Approved by someone

Approved.

I am not doing translations as much as forks which change existing translations, because I am running a small experiment and I picked this kata as a guinea pig: I want to turn it into an example of authoring practices so others could use it as an example to guide new authors about creating kata, tests, setting up snippets, etc. Whether it will work out well or not, we will see. I have not finished yet :)

If you want to make your translation conformant with the idea, please take a look at tests of C or NASM translation and make this one as similar as possible w.r.t. orgaization of tests, test groups, feedback on failure, dedicated generators for various types of inputs, etc. I can write a comment on the translation with explicit points I would like to have changed, if you want. If you don't want to, I can just merge it as it is and I will adapt it later.

Thanks for the translation!