Accept a special value "null" for LOG_DESTINATION #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This parses a new value
"null"
as aLogDestination
. On non-Windowssystems, it'll be equivalent to
"@/dev/null"
. On Windows systems,"@\\.\NUL"
(an explicitly-namespaced form for theNUL
device1).Closes #50.
I chose not to investigate the open question about whether or not
LOG_DESTINATION=NUL
would already Just Work. I decided it didn'tmatter, for two reasons:
While it's likely "specifying
NUL
" may conceptually work, it's verypossible you still need to practically use
LOG_DESTINATION=\\.\NUL
to do it.
That would not be very discoverable and the escaping required would
be quite error-prone, making the
null
sugar valuable.Mixed-OS teams attempting to have null as a default in (e.g.)
.env
can't do so today.
Without this sugar, such teams would have to concretely pick
/dev/null
orNUL
.Together, this seemed like enough to warrant the small bit of alias
complexity.
Footnotes
https://stackoverflow.com/a/58177337 ↩