New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make utilities work with non-UTF-8 inputs #554
Comments
The problem is that getopts returns See also #203, rust-lang/getopts#28 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Arcterus the bot seems misconfigured, it's marking accepted issues as stale. |
I configured the bot this way. |
For that definition, it is indeed stale, however it is still an open issue. Marking actual issues as "closed" hurts the community. Why do this? |
Because keeping bugs open for years without any activity isn't providing any benefit for anyone and reopening bugs is cheap. |
Reopening bugs is cheap for you, in that it annoys somebody else. I'm sorry you want to treat your community this way, but you can do what you want. Luckily the real coreutils treat product quality better. If you're happy being a toy reimplementation rather than providing a usefuly rewrite, that is a valid choice. You should probably update your README though. |
@remram44 I think you're going a bit too far there. @sylvestre I'm not sure why you would want to close an issue for a bug just because there hasn't been activity. It's not like the bug has disappeared. If anything, I think this just makes it harder to keep track of things. It's fine to mark stuff as stale, but only stale PRs should be closed IMO. Also, I don't actually think this is stale. All the PRs switching from |
Yeah, you probably saw that I opened plenty of good first bugs for this. ;) |
Well, this bug encompasses more than just switching to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Since the
String
types in Rust are by nature UTF-8, many of these utilities make the implicit assumption that all inputs will be UTF-8 encoded. It might be useful to expand the capabilities to include non-UTF-8 string handling as well. #553 does this forexpand
andunexpand
, but many other utilities don't fare so well (e.g.,fmt
).The text was updated successfully, but these errors were encountered: