Rakuyo

You are really careful and thought of using `startIndex` and `endIndex` to enhance the robustness of the code when it comes to indexing, which is really great!

> stride by 1 > > 1. `stride(from: x, to: y, by: 1)` to `x ..< y` > 2. `stride(from: x, through: y, by: 1)` to `x ... y` >...

> I think we should handle the stepping of index from the `indices` property of the `Collection` type. Because index is not always of `Int` type. Indeed.You're right. ---- I'll...

@krahets I have completed the review.

> SwiftUI template is the new default, the UIKit one is gone. You don't need to specify the template when using tuist init. Wanna contribute to them docs? 😁 So...

> @rakuyoMo Tuist supports UIKit, but we don't have a template. You can check out [the fixtures](https://github.com/tuist/tuist/tree/main/fixtures) directory in the repository for some examples that use UIKit. For example [this...

I need this too, and I want to initialize everything explicitly rather than relying on some speculative default value.

This feature is still important to me, and I understand that it seems like there are already other implementations for other platforms, but only iOS doesn't have it yet? If...

An idea that may have nothing to do with this PR (but this PR gives me some hope): `organizeDeclarations` will change the order of the code. It would be great...

> I was thinking about custom parameterization, but i could not achieve anything pretty. > > Things get weird where it comes for `custom` visibility & `custom` type. Currently we...