Why not treat h-18, h-19, etc. as an arbitrary value?

[pejrich]

It's one of the things I find frustrating about Tailwind. The values seem to be unintuitive. h-12 h-14 h-16 ...NO h-18 NO... h-20. I find myself on quite a number of occasions having to ask "What values are available to me again?". But since there's already automatic treeshaking of unused classnames, AND the ability to use any arbitrary value, sure, I know I can do h-[4.5rem] and it would be the same as there being a h-18, but it means I have to figure out what the missing value is each time, and I'm not that smart, so I forget very quickly. Why not just treat h-18, or even, h-19, as being the same as h-[4.5rem] and h-[4.75rem]. It seems like while sure, maybe it's a small inconvenience, it doesn't really need to be there since Tailwind is already parsing the code for arbitrary class names, and Tailwind is already filling in spots dynamically, so why not touch those two ends together and fill in the numbering gaps in the base classes dynamically, too?

Another example of this is 42. Not only is it the answer to life, the universe and everything, but it also has factors 1,2,3,6,7,14,21, and it feels much more like a number that would be used in a layout system, but we skip straight from 40 to 44, which fits less naturally to my intuition. I understand the logic when I look at the whole sequence, but when I'm actually using the classes in the real world, i'm regularly caught by that one too.

Thank you for all your hardwork. Despite my above comment, I do generally very much enjoy Tailwind and all that it does. So thanks for all that you do.