Time comparison fails on equivalent fractions about go-mtree HOT 2 CLOSED

would an individual check for the "time" keyword in check.go be too ugly? based off of how we actually test the file spec keyval against the actual file, it doesn't seem like string comparison can fully resolve this issue.

this also brings me to the idea of defining/implementing KeyVal checks for each keyword, so that instead of doing if string(kv) != curKeyVal, we can call something along the lines of checkKeywordFunc(kv,curKeyVal). I'm not sure how most KeyVal checks would differ from a string comparison, though, but this would avoid cluttering in check.go if we need to do some specific testing on keywords and possibly allow for flexibility and more accurate validation. thoughts?

from go-mtree.

@Stephen679 i think string comparison is fine. The issue here was fairly simple.

from go-mtree.