@LionC Thank you for the clean-ups!

I mostly agree with these changes, but I'm not in favor of moving test files into their own folder. Other std modules put the test files next to the implementation, and in my view that flat structure is easier for the collaborators to work with because the corresponding implementations and tests are close to each other.

@LionC Thank you for the clean-ups!

I mostly agree with these changes, but I'm not in favor of moving test files into their own folder. Other std modules put the test files next to the implementation, and in my view that flat structure is easier for the collaborators to work with because the corresponding implementations and tests are close to each other.

The only problem I see with the current structure is that we explicitly allow importing single functions from this folder, which means users of the module need to navigate it.

I work on the module a lot right now, and even I have a hard time to reorientate myself at a glance when opening the folder, there is just a lot of files with similiar names directly next to each other, some being tests and some being implementations without a consistent ordering pattern (because of the default alphabetical sorting everywhere).

My opinion on this is not super strong, but I can say that working on the module and scanning the folders at a glance is already a lot nicer after moving the test files. I will leave final judgement to you and the others though :-)

I will leave final judgement to you and the others though :-)

Test module next to the module being has been the way since the start and is the convention everywhere else so let's not randomly break from that for collections.

Done, please re-review @kt3k