Daniel Keep

The only change I'd make is replacing "the `Pod` trait" with "the `NoUninit` and `AnyBitPattern` traits" on line 50. If someone sees "Using Your Own Types" and jumps down directly...

I'm currently trying out some runtime scanners for [`scan-rules`](https://crates.io/crates/scan-rules). Basically: I want users to be able to parse text based on `Pattern`s (_e.g._ accept anything that matches this pattern, consume...

Oh, another thing I just realised: there doesn't appear to be any way to find out how _long_ a match is given a pattern and, say, `str::starts_with`.

I've had a look at this, and it looks like this only works _by coincidence_. To test this, I set up a new crate `scan` that depended on both `scan_macros`...

So, the problem with this is that it breaks backward compatibility. Everyone who was using this macro will now have to `use` the trait to get at the generated method....

**Son of a bitch.** *_sobs_* brb, writing `:vis` matcher RFC...

RFC: rust-lang/rfcs#1575.