Tracking issue for CommandExt::show_window

[andyolivares]

Feature gate: #![feature(windows_process_extensions_show_window)]

This is a tracking issue for #126690.

The idea is to expose STARTUPINFOW.wShowWindow in CommandExt trait to control how a new process' window is displayed on Windows OS (normal, minimized, maximized, etc.)

Public API

// std::os::windows::process

#[stable(feature = "windows_process_extensions", since = "1.16.0")]
pub trait CommandExt: Sealed {
  #[unstable(feature = "windows_process_extensions_show_window", issue = "127544")]
  fn show_window(&mut self, cmd_show: u16) -> &mut process::Command;
}

Steps / History

• Implementation: Exposing STARTUPINFOW.wShowWindow in CommandExt trait #126690
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[BlackHoleFox]

+1 for this in std. Had a use case for this managing processes on a desktop OS and this was a infinitely cleaner option compared to rolling my own, correct, CreateProcessW code just to set a single flag.

[andyolivares]

I've been using this myself in a production app with no issues since the feature was merged to master. I don't think a simple flag can cause much trouble :)

Can @dtolnay help us on stabilizing this feature? Thanks!

[andyolivares]

Stabilization Report

Implementation History

• Added function show_window() in CommandExt trait to expose STARTUPINFOW.wShowWindow flag: Exposing STARTUPINFOW.wShowWindow in CommandExt trait #126690
• Implemented the function in

  rust/library/std/src/sys/process/windows.rs

  Line 367 in 3f98535

  if let Some(cmd_show) = self.show_window {

API Summary

A summary of the API is included at the top of this tracking issue

Experience Report

At least two persons have been using this feature in production applications since Aug 2024.

---

Please @dtolnay can you help me start an FCP to make this feature stable?

[andyolivares]

Don't mean to bother, but maybe @Amanieu, @BurntSushi, @joshtriplett, @m-ou-se or @sfackler can also help starting an FCP for this feature? Thank you :)

[joshtriplett]

We reviewed this in today's @rust-lang/libs-api meeting, and we're happy to stabilize this. And the signature looks correct.

@rfcbot merge

Also, in the course of looking at this, we realized that the other similar methods should not have a startup_info_ prefix.

[rust-rfcbot]

Error encountered:
Provided team `` is invalid

[joshtriplett]

@rfcbot merge libs-api

[rust-rfcbot]

Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @the8472

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.