`forc-fmt` issue on `raw_ptr::write`.

Description

pub fn write<T>(self, val: T) {
        if __size_of::<T>() == 0 {    } else if __is_reference_type::<T>() {   // <---- look here how strange it is
        asm(dst: self, src: val, count: __size_of_val(val)) {
            mcp dst src count;
        };
    } else if __size_of::<T>() == 1 {
        asm(ptr: self, val: val) {
            sb ptr val i0;
        };
    } else {
        asm(ptr: self, val: val) {
            sw ptr val i0;
        };
    }
    }

Contributor guide

Tech stack

rust

Domain

clideveloper experience

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Basic knowledge of Sway syntaxFamiliarity with forc fmt tool

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

50

Research direction

The issue references PR #7620 which demonstrates a formatting bug in raw ptr::write where an else if block is oddly indented. To fix, examine the forc fmt source code (likely in swayfmt) to understand how it handles indentation of else if chains, especially when inline comments are present. Focus on the formatting logic for if else statements and ensure that comments within conditionals are correctly handled. Start by reproducing the issue with the provided code snippet.