Philipp Wendler

Hm, maybe because it is not obvious to find? Interestingly, in the last two days I found already two cases where I would use such a method in our code...

I also prefer `reversed` and used `reverse` only because of the existing method. I wonder whether all these methods should be marked as `@Deprecated` and methods named `reversed` be added?...

If measurements for the full experiment are enough, I can recommend using cgroups for measurements. It allows to measure CPU time and (max) memory usage for whole set of processes...

Any news on this? Is there anything we need to do?

No worries, just wanted to know whether there is something we need to do.

Is there still a chance that this will be merged at some point?

Yes, from a functional point of view there is no problem, there is just the overhead that was the cause for rejection in the past. Not sure how many users...

An automatic check for unwanted dependencies would be really good, because building the binaries is getting more and more complex. For example, currently we need to build MathSAT on something...

This [script](https://github.com/borgbackup/borg/blob/master/scripts/glibc_check.py) could be used as inspiration for such a check.

Other scripts that could be an inspiration are in these [LWN comments](https://lwn.net/Articles/771844/). Of course, if we use a container solution to implement #125 this check is not so important anymore.