Stringer for rule forgets ordering about gonids HOT 3 CLOSED

One possible method to address this is to take Tags that care about position (like byte_test, etc.) and promote them to a struct. We could then add an ordering index to all things where position matters (Content, PCRE, etc).

This would be ugly to find the correct component to write to string though.

from gonids.

Possibly we have an interface that is something like "Matcher" which each of these things (Contents, PCRE, etc) implement (all of them must implement String(), and shove all of these into a []Matcher{} at this point the stringer can still just loop through the slice once for each item.

from gonids.

This was fixed with #49

from gonids.