Marc Busqué

Thanks for getting back, @flash-gordon. I'm failing to understand the inconsistency with the constructor, shouldn't we use `Failure([:error, :message])` when using it? :thinking:

I see. Do you see it as something we could change in a major release (including the constructor)? Surely not the end of the world, but it's a pity we...

For context, I'd like to use it for the code at https://github.com/dry-rb/dry-operation/pull/6

> How did you come across this issue? While working on `dry-operation`, we need to [unwrap intermediate steps (or `throw` on failure)](https://github.com/dry-rb/dry-operation/blob/db90f8f8c2438b59c89cab9c7c4205a25d488ce7/lib/dry/operation.rb#L83-L91). That needs to be done blindly, without knowing...

For those with the same issue, consider using https://github.com/jiangmiao/auto-pairs instead of vim-autoclose. The incompatibility with neocomplcache disappears..

Have you considered something like doctest? I see there is an implementation in ruby: https://github.com/p0deje/yard-doctest The step missing would be bringing to life the following function: `f(yard, doctest) :: guides`

> instruct crawlers not to crawl individual versions, and only have then crawl latest documentation. Are we sure it is a good idea? What about if someone is using an...

Thanks, @loicginoux. I hadn't thought about that, and having an extra layer of security is good. Although, technically, as we're checking the event signature, we should be safe.

@elia, if I'm not wrong, the file won't be copied unless the private `specs=all` option is given during installation. Moving it to the `lib/` folder probably makes sense.

Thanks for your feedback, @loicginoux! > the event creation date (the event payload contains a created_at) is not a good source of truth. The last created is not necessarily the...