Repository navigation
Support all formatting flags in std::path::Display #44048
Description
Activity
- addedC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCP-lowLow priorityLow priorityregression-from-stable-to-stablePerformance or correctness regression from one stable version to another.Performance or correctness regression from one stable version to another.T-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]
on Aug 22, 2017 - addedA-fmtArea: `core::fmt`Area: `core::fmt`I-libs-radarLibs issues that are tracked on the team's radar.Libs issues that are tracked on the team's radar.
on Jul 31, 2020 I'd like to make a test case here but I'm unclear on what the issue is. The PR (#43830) that closed #43765 added tests for the width/fill/alignment formatting flags, and I can't think of what other flags would apply to Path. I'm also not sure what "it" refers to in the sentence "not just when it's conveniently already a &str". However, given that Alex made this issue while discussing the PR, I assume he had something in mind here, so I'm hesitant to close this outright.
- addedC-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.and removedregression-from-stable-to-stablePerformance or correctness regression from one stable version to another.Performance or correctness regression from one stable version to another.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC
on Jul 28, 2021 - addedE-help-wantedCall for participation: Help is requested to fix this issue.Call for participation: Help is requested to fix this issue.
on Jul 28, 2021 Relabeling this as a feature request rather than a regression, considering four years have passed without any comments here requesting for it.
@alexcrichton Can you clarify which flags you are talking about here? See the above comment.
Not that I remember 2017 off the top of my head, but rereading here I believe that the issue is that
Paths which are valid utf-8 follow formatting flags correctly, but paths which are not valid utf-8 may not. I suspect at the time I was sure that invalid utf-8 paths did not follow formatting flags, but I'm not sure if that's the case still.Reacted by bstrie
This regression was initially noted in #43765 which was caused in #42613 where this struct in the standard library no longer respects all formatting flags. This is a tracking issue for supporting all formatting flags all the time, not just when it's conveniently already a
&str.