Position of RBS::Location should be byte length about rbs HOT 3 OPEN

I think we need both of character position and byte position, based on the use cases.
Storing byte positions and calculate character position when we need, like Prism, might be a good way.

from rbs.

I'm concerned about that it introduces performance degradation if RBS calculates a character position from a byte position. Currently, RBS uses only character positions at the Ruby level; therefore, it will need the calculations for every RBS::Location usage.

from rbs.

We can use a workaround to temporarily avoid the issue by utilizing methods like start_loc and end_loc to ignore the effects of comments.

from rbs.