Nested call chains have weird formatting

/// Returns n_1, b_1, n_2, b_2
fn distribute(sum: u64) -> (u64, u64, u64, u64) {
    let mut a = sum;
    // ...
    if a == 1 {
        // ...
    } else {
        let kmax: u64 = a.ilog2().into();
        let pow_2_kmax: u64 = (2_i32
            .pow(kmax.try_into().expect("k_max could not convert into u32")))
        .try_into()
        .expect("2^(k_max) could not convert to u64");
        return (kmax + 1 + m, 1, a - pow_2_kmax + 1 + m, a - pow_2_kmax);
    }
}

What I would expect:

/// Returns n_1, b_1, n_2, b_2
fn distribute(sum: u64) -> (u64, u64, u64, u64) {
    let mut a = sum;
    // ...
    if a == 1 {
        // ...
    } else {
        let kmax: u64 = a.ilog2().into();
        let pow_2_kmax: u64 = (2_i32
                .pow(kmax.try_into().expect("k_max could not convert into u32")))
            .try_into()
            .expect("2^(k_max) could not convert to u64");
        return (kmax + 1 + m, 1, a - pow_2_kmax + 1 + m, a - pow_2_kmax);
    }
}

Can you do a better job explaining what the issue is?

The issue is that it is not indenting the function calls like it normally would.
Usually, it indents like this:

    stdin()
        .read_line(&mut file_path)
        .expect("Eingabe konnte nicht eingelesen werden!");

But in the example I provided, they are all in the column where the base calls/assignments/definitions usually are

There's something about wrapping 2_i32.pow(kmax.try_into().expect("k_max could not convert into u32")) in parens that's causing the issue. The following formats just fine:

Input

/// Returns n_1, b_1, n_2, b_2
fn distribute(sum: u64) -> (u64, u64, u64, u64) {
    let mut a = sum;
    // ...
    if a == 1 {
        // ...
    } else {
        let kmax: u64 = a.ilog2().into();
        let pow_2_kmax: u64 = 2_i32
            .pow(kmax.try_into().expect("k_max could not convert into u32"))
        .try_into()
        .expect("2^(k_max) could not convert to u64");
        return (kmax + 1 + m, 1, a - pow_2_kmax + 1 + m, a - pow_2_kmax);
    }
}

Output

/// Returns n_1, b_1, n_2, b_2
fn distribute(sum: u64) -> (u64, u64, u64, u64) {
    let mut a = sum;
    // ...
    if a == 1 {
        // ...
    } else {
        let kmax: u64 = a.ilog2().into();
        let pow_2_kmax: u64 = 2_i32
            .pow(kmax.try_into().expect("k_max could not convert into u32"))
            .try_into()
            .expect("2^(k_max) could not convert to u64");
        return (kmax + 1 + m, 1, a - pow_2_kmax + 1 + m, a - pow_2_kmax);
    }
}

Navigation Menu

Repository navigation

Nested call chains have weird formatting #7119

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Nested call chains have weird formatting #7119

Description

Activity

ytmimi commented on Sep 13, 2026

Xyndra commented on Sep 13, 2026

ytmimi commented on Sep 14, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions