I'm always wary of naming my classes according to performance criteria. What if you (or someone else) finds a faster method of reading tokens from an input stream. Would you then write an EvenFasterReader? How about something like TokenReader?

Consider letting the user pass the delimiters as well (optionally). This will make it more useful by allowing to parse input which is delimited by other things than white spaces.

I'm always wary of naming my classes according to performance criteria. What if you (or someone else) finds a faster method of reading tokens from an input stream. Would you then write an EvenFasterReader? How about something like TokenReader?

Consider letting the user pass the delimiters as well (optionally). This will make it more useful by allowing to parse input which is delimited by other things than white spaces.

I'm always wary of naming my classes according to performance criteria. What if you (or someone else) finds a faster method of reading tokens from in input stream. Would you then write an EvenFasterReader? How about something like TokenReader?

Consider letting the user pass the delimiters as well (optionally). Will make it more useful by allowing to parse input which is limited by other things than white spaces.

I'm always wary of naming my classes according to performance criteria. What if you (or someone else) finds a faster method of reading tokens from an input stream. Would you then write an EvenFasterReader? How about something like TokenReader?

Consider letting the user pass the delimiters as well (optionally). This will make it more useful by allowing to parse input which is delimited by other things than white spaces.