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.

Sign up for GitHub

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

Jump to bottom

Move thrill's Aggregate and StatsTimer to tlx #13

Open
lorenzhs opened this issue Sep 20, 2018 · 3 comments
Open

Move thrill's Aggregate and StatsTimer to tlx #13

lorenzhs opened this issue Sep 20, 2018 · 3 comments

Comments

@lorenzhs
Copy link
Contributor

They make much more sense in tlx, mostly because they're more generally useful and I want to use them.
@bingmann
Copy link
Member

Aggregate ... maybe, it is almost (but not fully) identical in another project.
StatsTimer ... dunno, there are so many timer variants.

@lorenzhs
Copy link
Contributor Author

lorenzhs commented Sep 21, 2018 •
edited
Loading

There are also a lot of loggers, command-line parsers, and thread pools ¯\_(ツ)_/¯

Why don't we factor out the common bits of Aggregate (with a better name) into tlx, and derive from that in Thrill and the other project:tm:?

@bingmann
Copy link
Member

Yes. Aggregate is okay. Timers are hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lorenzhs @bingmann