-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Figure out what to do with our uses of builtins.match before Nix 1.12 is released #28718
Comments
I can look at the idris usage of Eventually I think I will refactor that code anyway to not rely on |
It now uses |
Here's one difference which I noticed with non-matching capture groups:
|
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
it's been five years. any issues that were likely to ever be discovered probably have been, and if there's anything left this issue probably won't even be remembered by whoever finds it. |
A quick
git grep
against a recent HEAD reveals that we use builtins.match fairly extensively:We need to figure out which regexes will be affected by the change (if any) and fix them.
Also, many of them already behave differently between Linux and Darwin (see NixOS/nix#1537), so we should probably do something about those even before 1.12 😄
The text was updated successfully, but these errors were encountered: