Skip to content

Conversation

sunfishcode
Copy link
Member

We don't actually do anything different for different errno values, other than panic on unknown ones, and that isn't that isn't adding much value compared to the cost of being an extra surprise when porting to new OS's.

Fixes #467.

We don't actually do anything different for different errno values,
other than panic on unknown ones, and that isn't that isn't adding
much value compared to the cost of being an extra surprise when
porting to new OS's.

Fixes #467.
@sunfishcode sunfishcode merged commit ce30bd9 into main Dec 1, 2022
@sunfishcode sunfishcode deleted the sunfishcode/isatty-no-errno branch December 1, 2022 19:03
@ahl
Copy link

ahl commented Dec 5, 2022

Any chance we could get a new release with this PR included? Thanks!

sunfishcode added a commit that referenced this pull request Dec 5, 2022
We don't actually do anything different for different errno values,
other than panic on unknown ones, and that isn't that isn't adding
much value compared to the cost of being an extra surprise when
porting to new OS's.

Fixes #467.
sunfishcode added a commit that referenced this pull request Dec 5, 2022
We don't actually do anything different for different errno values,
other than panic on unknown ones, and that isn't that isn't adding
much value compared to the cost of being an extra surprise when
porting to new OS's.

Fixes #467.
@sunfishcode
Copy link
Member Author

This is now released in 0.36.5!

@sunshowers
Copy link
Contributor

Thanks @sunfishcode!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

isatty is not required to set errno
3 participants