swithek

@ysomad The core functionality of that fork is the same as ozzo-validation's, which means the performance is also the same. I haven't compared this with https://github.com/go-playground/validator but I also don't...

@oliy I've merged your changes to the fork of this repository: https://github.com/jellydator/validation. The plan is to actively maintain it, so if you have any other changes, you can submit a...

I'm closing this PR since the same result can already be achieved in the latest version.

That's quite strange. These functions haven't been changed since they were first implemented/updated in the original repository, so I cannot answer why these inconsistencies exist, but we can certainly discuss...

Yes, that sounds good to me. Feel free to open a PR whenever you want!

I think you are right and this might be a good change. Before we merge this, have you done any benchmarking here? I am asking because of this bit: >...

> > I think you are right and this might be a good change. Before we merge this, have you done any benchmarking here? I am asking because of this...