Tracking issue for PathBuf capacity methods

[Mark-Simulacrum]

• capacity
• with_capacity
• clear
• reserve
• reserve_exact
• shrink_to_fit
• shrink_to, should probably not be stabilized before OsString::shrink_to, see Tracking issue for shrink_to feature #56431

[aaronstillwell]

Happy to take this on as a first contribution to rust.

[Mark-Simulacrum]

Great! I'd be happy to help you get started, just let me know if you want mentoring/instructions at any level!

[aaronstillwell]

@Mark-Simulacrum are you able to define a list of the methods that need to be implemented as part of this PR?

[Mark-Simulacrum]

I think all of these will essentially call the underlying functions on OsString.

• capacity
• with_capacity
• clear
• reserve
• reserve_exact
• shrink_to_fit
• shrink_to -- this one is more of a maybe, since it's unstable on OsString. We can reuse the same tracking issue for this.

We'll probably want to add all of these under the same feature gate.

[aaronstillwell]

@Mark-Simulacrum thanks for that. I have the implementation drafted locally. I'm having some difficulty however in running the tests for stdlib - even a cargo check is producing errors not related to my changes. Is there any documentation I've missed for best practices on compiling / working on stdlib?

[Mark-Simulacrum]

You'll want to use x.py; for your scenario I believe x.py test --stage 0 src/libstd and/or x.py check src/libstd are the commands you want. I'm not sure where the most current documentation is.

[ordovicia]

This page on rustc guide describes how to use x.py.