@pYtato-KK, updated the previous message with the exact quotation.
No thanks)))

From the Unpriviliged ISA spec of Ch.I, p.1:

We also pun on the
use of the Roman numeral “V” to signify “variations” and “vectors”, ...

"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.

What's about my solution... So this is my solution))
And yours is yours))
No one obliged to understand what is going on except those approving it.
And what more important is that V in RISCV is also intentionally to emphasize Vector.
So it's a bit odd to write in RISCV and not use V when it is possible))

And also it's a great chance for warriors to start learning V while seeing its usage with some explanation.

To my and to traditional C programmers misfortune some RISCV kata were even translated by not C programmers but some colledge/university students and some higher level languages.

So i do apologize for being so traditional and also for respecting Brian Kernighan and Dennis Ritchie style!

             *   *   *   *   *

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?