Need access to OS specific `PATH_SEPARATOR`

[calebdw]

Hello!

I need access to the PATH_SEPARATOR constant that contains the OS specific PATH separator used by std::env::split_paths:

rust/library/std/src/sys/pal/unix/os.rs

Lines 25 to 31 in f7b4354

	cfg_if::cfg_if! {
	if #[cfg(target_os = "redox")] {
	const PATH_SEPARATOR: u8 = b';';
	} else {
	const PATH_SEPARATOR: u8 = b':';
	}
	}

It would be great if this could be exposed similarly to the MAIN_SEPARATOR{,_PATH} constants:

rust/library/std/src/path.rs

Lines 259 to 270 in f7b4354

	/// The primary separator of path components for the current platform.
	///
	/// For example, `/` on Unix and `\` on Windows.
	#[stable(feature = "rust1", since = "1.0.0")]
	#[cfg_attr(not(test), rustc_diagnostic_item = "path_main_separator")]
	pub const MAIN_SEPARATOR: char = crate::sys::path::MAIN_SEP;
	/// The primary separator of path components for the current platform.
	///
	/// For example, `/` on Unix and `\` on Windows.
	#[stable(feature = "main_separator_str", since = "1.68.0")]
	pub const MAIN_SEPARATOR_STR: &str = crate::sys::path::MAIN_SEP_STR;

Thanks!

[lolbinarycat]

I believe this would need to be an ACP

[calebdw]

Turns out I can just use std::env::join_paths instead of manually doing it myself---however, exposing the constants might still be useful (otherwise feel free to close this)

[lolbinarycat]

Exposing this would require a compelling usecase, which has not been presented. Even if a compelling usecase is found, it should be presented in the form of an ACP, not here, so I'm closing this.