fix: formatting for loop

[amiremohamadi]

Description

Fix #6804

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[zees-dev]

Nice; tested and seems to be working 👍

[JoshuaBatty]

This doesn't solve the issue.

There is already white space added after the for keyword so this change just pads more white space.

Locking this while I look into it.

[zees-dev]

This doesn't solve the issue.

There is already white space added after the for keyword so this change just pads more white space.

Locking this while I look into it.

I manually tested switching to the PR branch to validate.
Weird, there maybe a deeper underlying issue then; thanks for looking deeper!

[JoshuaBatty]

This looks like a parser error. If we take the example for from the linked issue and run it we get a parser error. @IGI-111 any idea why the parser would be failing here?

#[test]
fn contract_for_loop() {
    check(
        indoc! {r#"
        contract;

        abi MyContract {
            fn test_function() -> bool;
        }

        impl MyContract for Contract {
            fn test_function() -> bool {
                let mut my_vec: Vec<u64> = Vec::new();
                for iter in my_vec.iter() {

                }

                true
            }
        }
        "#},
        indoc! {r#"
        contract;

        abi MyContract {
            fn test_function() -> bool;
        }

        impl MyContract for Contract {
            fn test_function() -> bool {
                let mut my_vec: Vec<u64> = Vec::new();
                for iter in my_vec.iter() {

                }

                true
            }
        }
        "#},
    );
}

thread 'contract_for_loop' panicked at swayfmt/tests/mod.rs:9:86:
called `Result::unwrap()` on an `Err` value: ParseFileError(ParseFileError([Parse { error: ParseError { span: Span { src (ptr): 0x149a04180, source_id: None, start: 95, end: 101, as_str(): "my_vec" }, kind: ExpectedKeyword { word: "in" } } }]))

[amiremohamadi]

@JoshuaBatty thanks for the review! The issue isn't with adding a space after the for keyword, but rather with AmbiguousSingleIdent. In this case, it treats

for iter in my_vec.iter() {
}

as if it was written like:

for iterin my_vec.iter() {
}

[IGI-111]

Fixing the in keyword handling seems to do the trick, but @amiremohamadi can you add a test that validates the example from the issue that Josh is quoting here?

[kayagokalp]

Seems like we have couple conflicts @amiremohamadi before we can continue running the CI

[amiremohamadi]

@kayagokalp rebased my changes