Brandon Weaver

Hrm. That'd break the API as it exists. It assumes a key or method is present. I _could_ potentially make === work on keys as a last comparator but that'd...

Example: ```ruby contract = Qo.contract.all(Symbol => Integer) contract.call(a: 1, b: 2) # => true contract.call('a' => 1, b: 2) # => false ``` There would have to be an additional...

(though now I almost wonder if this is another gem entirely as Qo itself doesn't behave like this)

Musing on it a bit, it seems like the only way to get it to work is to make a distinction between 1-item and true multi-arity lists. The problem is...

Looking back on this issue, I believe it would add too much magic to the API. It would likely be better suited as an extension implementing some of the same...

Ah, I've noticed that there's range support in the Ruby version blocks. Would that be the recommended way? EDIT - Went ahead and added that in, going to assume so.

I'll take on a few pattern matching items: * One-line match (`=>`) [Feature #17260] * One-line match (`in`) [Feature #17371] * Find pattern [Feature #16828]

Will wait to go after Feature #16828 until I understand conventions for contributing to this repo.

Feature#16378 (Argument forwarding with leading arg) had been completed by the following commit: https://github.com/ruby/spec/commit/b089bf7817d1fbe76d1ab752cb3744724bb2a825

While resolving this issue is all well and good with a patch, it needs to work out of box. I'll look into getting a PR for this out later. It...