Thank you. Wonderful suggestions. I like the second idea more.

you can't make a meaningful kata if the compiler is giving away the exact code that you have to type in to make it work.

You are right.

I changed the signature, so the compiler does not show the solution, but helps to figure it out. And more; if you use the compiler it suggests the wrong fix at first.

I cannot find the first kata, i solved on codewars. But it was such a task to add { to a function signature.

But i found this one: https://www.codewars.com/kata/50654ddff44f800200000004
Is this not relevant to your issue? The compiler says, what you can do to fix.

Can i extend the kata to solve your issue?
This is a fundamental concept of rust to show. I want to focus on this concept, but without any need to change the function implementation code. Maybe you have a suggestion.

Thank you for your input. I am a beginner for rust and codewars, so i want to learn more about both while i create a kata. So i try to figure out, how to handle static lifetimes. But currently i have no clue.

Hey. Thanks for your comment. There are katas already with missing characters like ; or {, which can be autofilled by compiler. So I thought it would be a good idea to create a kata to show a first example about the lifetime concept of rust. And for a kyu 8; is it not okay to learn to work with the compiler messages?

Done. Thanks