You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As is typical on that platform, Windows defines a SearchPath macro to choose between SearchPathA and SearchPathW. The macro conflicts with our struct name.
NixSearchPath, or do we have an alternate term for this concept?
Doesn't hurt to qualify it anyway. There's other search paths out there, like PATH, etc, and we interact with those too.
LookupPath is an option, since the docs also use that.
I would like to avoid Nix since it is already in the Nix namespace. Similarly, I regret putting Nix in NixStringContext, which was a silly mistake on my part.
As is typical on that platform, Windows defines a
SearchPath
macro to choose betweenSearchPathA
andSearchPathW
. The macro conflicts with ourstruct
name.Originally posted by @Ericson2314 in #8901 (comment)
The text was updated successfully, but these errors were encountered: