tree 0fe8d0ed90ca51f6c95db27486f53a66d4ce2d59
parent 69fdf3010a9a179c3fbbe3d7e2ca1f461b44d874
author Natalie Weizenbaum <nweiz@google.com> 1548720083 -0500
committer GitHub <noreply@github.com> 1548720083 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJcT5fTCRBK7hj4Ov3rIwAAdHIIAEjGTShq6HfUjfRrgLQcfBZu
 WVv5uQhZJwdcn3ptidyYEkBbOd+PNYdK1r30n6CZNxAnG0Q3jGtahxNzQH8qjjXO
 9nX3kZ7LmILPyl8CaiB91gHTDzOArybcrLu3szpSBLHM7EdvPB7HLjBMMpdytpos
 iqWY1e9I02SOD+HxnJVDgt7wG8+/6h9e62Z7q3j/3BZkJL7HJHabgQ70eQuwgBi3
 6CJ2SUH2QrQsAXR9TFARn6WC5crrLHK/vx1IiXV9YkOWRhbAFWQ43EAsz+XpSteI
 wfJ7d7mb1HuwTFia/V8cZM+R9MX0sfGXq8wWahfxbJv7rkntkopSRM52zZ7LJEE=
 =zv6H
 -----END PGP SIGNATURE-----
 

Drop special support for point spans at the end of files (#31)

Drop special support for point spans at the end of files

This broke point spans at the beginning of lines elsewhere in the
file. Unfortunately, there's no way to disambiguate these currently.
SourceSpanWithContext doesn't have any information about where the
span appears in the context, so for point spans at column 0, it could
be at the beginning of the line or after the trailing newline.

We should eventually add something like
SourceSpanWithContext.indexInContext, but that'll require a breaking
release, since downstream users implement FileSpan as an interface.