| Age | Commit message (Collapse) | Author | 
|---|
|  | The second next commit will move errors out of the Token enum
but we still want to be able to test that the spans of errors
are character encoding independent. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | I forgot to document this breaking change
in e993f19c2b8ef00b32f17f9ed32306f3ceb21bc3. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | While much of the span logic currently assumes UTF-8, we also
want to support other character encodings, such as e.g. UTF-16
where characters can take up more or less bytes than in UTF-8. | 
|  |  | 
|  |  | 
|  |  | 
|  | We'll reuse the field for another offset in the next commit. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | The tests for character reference errors should be grouped together.
So this commit puts "char_ref" first in the function name
(since our error tests are ordered by function name). | 
|  |  | 
|  | With codespan_reporting an empty span shows up exactly like a
one-byte span, which is why I didn't notice this mistake earlier. | 
|  |  | 
|  |  | 
|  |  | 
|  |  |