Ovid

If someone thinks this is interesting and wants to write a better PPC, please go for it. My wallet just got stolen and I have a **ton** of paperwork to...

Also, directly under `use feature 'say';`, I'd add this `say "Perl version is '$^V'";` Even if you think you're running the correct version of Perl, it's possible that something under...

The reason you can't do it after 'with' has run is that you lose the composition safety and that violates the entire spirit of what Role::Basic is trying to do....

@tobyink I'm sorry I didn't respond sooner. I've had other issues I've had to deal with. You say that `Data::Checks` should not touch `strict` and `warnings`, but you didn't explain...

(Deleted previous comment because I had names backwards) @tobyink I see your point now. You're absolutely right. If you or someone else would like to provide a PR, I'd be...

I think this sounds like a very reasonable thing. (*Edit*: Obviously, I needed to think about this more)

The problem with booleans as numbers/text/undef, is that there's no semantic information with them. Internally, that kinda works: was that `undef` supposed to be false or was it an uninitialized...

Currently I'm more concerned about the fact that Perl now has native `true` and `false` (thank goodness)!. This is currently not handled by `BOOL`, but I see that `Data::Checks::Parser` already...

I agree that `undef` cannot behave like `NULL`. I wish it did, but that ship has sailed. Otherwise, to answer @happy-barney's question, in [Data::Checks::Parser](https://github.com/Perl-Oshun/oshun/blob/main/lib/Data/Checks/Parser.pm#L48), we have this: ``` BOOL =>...

@druud We vetoed default values early on because they tend to be arbitrary. Just because something defaults to false doesn't mean it's false, for example. If we default `my UINT...