std: add cross platform null-device name

[WindSoilder]

Description

We have meet a discord discussion about cross platform null-device: https://discord.com/channels/601130461678272522/988303282931912704/1165966467095875624

I want the same feature too...And I think it's good enough to add it into nu-std.

Different to https://github.com/nushell/nu_scripts/pull/649/files, I think named it to null-device(the name comes from wiki) is better than null-stream.

[amtoine]

once we land this new command, could you remove the null-stream command from the nu_scripts @WindSoilder ? 😇

[amtoine]

thanks @WindSoilder for this and tweaking the code from review comments 🙏

[amtoine]

so if you get a minute to remove the candidate in the nu_scripts, that'd be perfect 😌

[Hullabaloo-and-Howdy-Do]

Redirecting to the virtual path that Windows uses does the job, but I think the proper way of doing it is actually to redirect to NUL:

[ChrisDenton]

\\.\NUL is the canonical win32 path, try using GetFullPathName on NUL. Things like NUL: are an old bit of wisdom from the days before UNC paths, device paths and file streams when it was used as an illegal file name that should always error if not redirected and thus shouldn't conflict with any real file. That's a more fragile assumption.

[Hullabaloo-and-Howdy-Do]

\\.\NUL is the canonical win32 path, try using GetFullPathName on NUL. Things like NUL: are an old bit of wisdom from the days before UNC paths, device paths and file streams when it was used as an illegal file name that should always error if not redirected and thus shouldn't conflict with any real file. That's a more fragile assumption.

Ahh, interesting. I wasn't aware of that, I had trouble finding any documentation on the null device and the NUL: thing was the only detail I could find. Good to know.