google
Print better messages for problems with tag filtering ranges
Right now, 0B:256B is interpreted at a range for filtering tags, but 0:256B is not.
I think we should either infer that the units are the same for both parts of the range if units are only specified for one half of the range, or not require units for zero.
We should also, perhaps, provide a message to indicate when something that looks like a range is being interpreted as a regexp.
I think complaining with a clear error message that units are different here would be sufficient to guide the user.
Make sense to me.
User originally started with "0:256" -- so perhaps we should also complain when there are no units.
For "0:256" I'd expect an error message that tag X has the unit of Y but unit Z was used in the filter.