That was the lazy answer; reading the code again, I guess we could support integers since we're densifying in `double` format anyway so there's no wraparound problem with the subtraction. But supporting lots of types does yield a blowup in the compile time and the question is which types are important. I keep my frequencies in `double` format because I want to normalize them, get fast dot products, etc.