You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On POSIX systems, there is a limit to the number of files that can be passed as arguments. I thought that limit was 1024 arguments, and I was wrong. It's complicated. It seems like the limit is actually counted on the amount of memory it takes instead of the number of argument. Or both. Depending on the system.
Apparently, on Linux it's currently 2MB, which probably enough with the type of projects that treefmt will deal with. At that size, other constraints in terms of performance improvement would change the project's design anyway.
At some point we might want to calculate if we reach that limit, and invoke the formatter multiple times, splitting the number of files equally between invocations.
On POSIX systems, there is a limit to the number of files that can be passed as arguments. I thought that limit was 1024 arguments, and I was wrong. It's complicated. It seems like the limit is actually counted on the amount of memory it takes instead of the number of argument. Or both. Depending on the system.
Apparently, on Linux it's currently 2MB, which probably enough with the type of projects that
treefmt
will deal with. At that size, other constraints in terms of performance improvement would change the project's design anyway.At some point we might want to calculate if we reach that limit, and invoke the formatter multiple times, splitting the number of files equally between invocations.
source:
The text was updated successfully, but these errors were encountered: