Saurabh Nanda

> could you describe the current testing process (prior to the implementation of a proper test suite)? there were simple "example based" tests primarily to ensure that the underlying raw...

@mrputty I've got the tests to compile again in the `fix/tests` branch. Although the tests themselves are still failing. I'll spend some time now in getting the tests up-to-speed.

@mrputty the "example based" tests are passing now. The property-based test is still commented-out. I'll take a look at it over the weekend.

@ivanbakel I'm working on some more breaking changes. Plan to release something in a week or two. Thank you for your patience.

Hey @aschmois great to know that you're planning to use `odd-jobs`. Do comment at https://github.com/saurabhnanda/odd-jobs/issues/44 when your implementation finally makes it to production. > The only current concern we have...

This is a good feature to have. I've added this to the [roadmap](https://github.com/saurabhnanda/odd-jobs/labels/roadmap)

@aschmois any thoughts on my previous comments?

Apart from the perf concerns, I was also wondering if there is any way we can support a simpler use-case: concurrency limits on a job-type basis. With this PR as-is,...

@mrputty @tommd @jkachmar @garethstokes Would you be kind enough to to share your thoughts on the following questions: - How are you using `odd-jobs`? - production / work-related project -...

> We are currently doing some initial scale testing with it. @mrputty if you are writing benchmarks, would it be possible to merge them upstream? If not the code, then...