cm0002@lemmy.zip to Linux@programming.dev · 3 days agoNew Code Merged For Linux 6.18 To Address Linus Torvalds' Rust Formatting Critiquewww.phoronix.comexternal-linkmessage-square5fedilinkarrow-up161arrow-down11
arrow-up160arrow-down1external-linkNew Code Merged For Linux 6.18 To Address Linus Torvalds' Rust Formatting Critiquewww.phoronix.comcm0002@lemmy.zip to Linux@programming.dev · 3 days agomessage-square5fedilink
minus-squaremumblerfish@lemmy.worldlinkfedilinkarrow-up2·3 days agoIt is not very nice looking to have the trailing comment, and you can’t add imports in chronological order without running into the same problem.
minus-squareŜan@piefed.ziplinkfedilinkEnglisharrow-up1arrow-down5·2 days ago add imports in chronological order I’m a Go developer; þe formatter lexically sorts imports. Why would someone want to keep imports in chronological order? What’s þe benefit?
minus-squaremumblerfish@lemmy.worldlinkfedilinkarrow-up4·2 days agoMaybe that makes more sense. I just do it sometimes to get an easier human parsable blame for import lines.
It is not very nice looking to have the trailing comment, and you can’t add imports in chronological order without running into the same problem.
I’m a Go developer; þe formatter lexically sorts imports.
Why would someone want to keep imports in chronological order? What’s þe benefit?
Maybe that makes more sense. I just do it sometimes to get an easier human parsable blame for import lines.