Skip to content
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

Backport 7447 to 2.13 maintenance #8763

Merged

Conversation

roberth
Copy link
Member

@roberth roberth commented Jul 31, 2023

Motivation

Solve the issue raised in

Context

Closes #8392 which I couldn't force push

Checklist for maintainers

Maintainers: tick if completed or explain if not relevant

  • agreed on idea
  • agreed on implementation strategy
  • tests, as appropriate
    • functional tests - tests/**.sh
    • unit tests - src/*/tests
    • integration tests - tests/nixos/*
  • documentation in the manual
  • documentation in the internal API docs
  • code and comments are self-explanatory
  • commit message explains why the change was made
  • new feature or incompatible change: updated release notes

Priorities

Add 👍 to pull requests you find important.

aakropotkin and others added 3 commits July 31, 2023 16:37
Allows checking directory entry type of a single file/directory.

This was added to optimize the use of `builtins.readDir` on some
filesystems and operating systems which cannot detect this information
using POSIX's `readdir`.

Previously `builtins.readDir` would eagerly use system calls to lookup
these filetypes using other interfaces; this change makes these
operations lazy in the attribute values for each file with application
of `builtins.readFileType`.

(cherry picked from commit 153ee46)
(cherry picked from commit 37c533e)
* Fixup release notes
@Ericson2314
Copy link
Member

I guess it is OK to skip some releases to backport since this is not a behavioral change?

@roberth
Copy link
Member Author

roberth commented Jul 31, 2023

It is not a behavior change except for builtins?readFileType which is not part of our implicit compatibility promise.

Also it can be argued to fix the buggy lib.pathType polyfill. If not technically buggy it is at least confusing, and that's worth fixing too.
It sure beats documenting and communicating the "limitations" of 23.05.

@Ericson2314
Copy link
Member

oh my bad I think i was looking at the wrong diff. If this is alreaydd in 2.14 (or 2.15 cause 2.14 is kinda of informally deprecated) no problem.

@infinisil
Copy link
Member

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.

5 participants