I accidentally used number[n] instead of number = [] and it gave me an error, lmao
very nice!

Fair point, I probably should've marked this as a suggestion instead.

I read on this array topic yesterday, but since I'm very new to the language and it is quite complex, I always imply that there's something I don't know instead, so there was a little confusion.

Perhaps this will help someone in the future. Cheers

This challenge is available in almost 30 languages, and sometimes it is difficult to keep descriptions generic :( It is somewhat expected that users will be able to navigate this kind of ambiguities, especially when the intended meaning is evident, and can be easily inferred from the initial solution setup and tests.

But yeah, ideally descriptions would not require any mental gymnastics, especially for white kata, where beginners can get easily confused.

In Rust, this exercise asks you to create an array, but expects a Vec (array elements have to be known at compile time, so creating an actual array is not possible, to my knowledge).

it works xd

The people who come up with beautiful solutions just have more experience and knowledge. Eventually you may reach these levels, or you may not, up to you to decide how far will you progress.

BF translation: https://www.codewars.com/kumite/68a425c20cf4fa60e1a5f950

You nailed it bro.

Thanks for the neat kata! A simple yet satisfying little sequence challenge.

That is an interesting solution)

Solid learning experience! Cool kata!

Thank you!

I don't understand where the reference solution finds additional user authorship. Regardless of whether I use the API or look at the user's page, the result is the same in my case. Ok, although it's not completely clear how it works, but as a huge hint, exactly 1 API request is needed.

I approved the fix. I reduced the number of random tests to 10 because I got several timeouts with 20 random tests.

Great