Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Is it a useful enough function to keep? It looks like the only time you'd notice the difference between GetenvError and Getenv is if you pass an empty key, or if you want to distinguish an unset environment variable from an empty-but-set one. The former case is trivially checkable from callers; the latter case can either use syscall.Getenv directly, or use os.Environ and parse/iterate themselves. Just my 2¢.
Labels changed: added priority-go1, removed priority-triage.
This issue was closed.