vemv

Yes, the generated artifact I can find in ~/.m2 lacks any sources, I only see a few meta files

Here's the repo in question (wasn't public before) https://github.com/vemv/eftest

I see the fix can be easy to implement https://github.com/Glavin001/atom-beautify/pull/141/files

For anyone else finding this issue, an alternative approach would be to use the antq [lein plugin](https://github.com/liquidz/antq/tree/eb3bd2d5f1f2351bbaa69a50f4ddd5973efd2423#leiningen-as-a-plugin) as a github action, and then [self-hosting a badge](https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)

Correction: Ruby [does have](http://ruby-doc.org/core-2.2.0/Mutex.html#method-i-try_lock) try_lock, but no `try_lock do ... end` which would be more useful.

> Would you be interested in helping define what the API for the atomics should look like? Personally I would be fine with most possible reasonable designs, as long as...

It might be CAS as an implementation detail, but for the user it's not CAS as it doesn't accept a comparison argument (see the Java API for compareAndSet)

> Personally I'm leaning against this Worth noting that there a different styles of testing. One size rarely fits all. An opt-in functionality surely doesn't hurt? > It's worth noting...

I think I understand your point: requiring users to expect specific values is not the average intended use of rspec-mocks. Perhaps my original proposition can be tweaked so it makes...

> this is a mocking and stubbing library I'd just like to point out that as an user, this fact is fairly irrelevant. I add `rspec` to my Gemfile, not...