User avatar
Jon Sterling @jonmsterling@mathstodon.xyz
1mo
I'm experimenting with representations of concrete syntax in OCaml...
open Algebra module type S = sig type content type offset type token_info type node_info type token = {info: token_info; content: content} type 'a node = {info: node_info; children: 'a list} type 'a layer = Token of token | Node of 'a node type tree = Tree of tree layer type cursor = {offset: offset; layer: cursor layer} val localise_tree : offset:offset -> tree -> cursor * offset val tree_content : tree -> content end module type Input = sig (** A homomorphism from a monoid of source code to a monoid of offsets. *) module Content : MonoidHom type token_info type node_info end
2
0
0
0
User avatar
Liam O'Connor @liamoc@types.pl
1mo
@jonmsterling could this at last mean that utf-16 offsets could be provided for full LSP compatibility?
2
0
0
0
User avatar
mio @mio@shrimp.mio19.uk
1mo
@liamoc Oh no utf-16. I remember converting back and forth between utf-8 and utf-16 when implementing a lsp server. It was not pleasant
1
0
1
0
User avatar
Liam O'Connor @liamoc@types.pl
1mo
@mio i don't like LSP and I don't like VSCode. It bugs me that it's so ubiquitous and Microsoft forced their shitty UTF-16 on everyone. Forester's LSP is currently utf-8 only and this means it works only with some LSP-enabled editors that are more permissive than the LSP spec is about available encodings. But Nova is unfortunately one of those editors that insists on UTF-16.
1
0
1
0
User avatar
mio @mio@shrimp.mio19.uk
1mo
@liamoc It would be great if there were a general translator between utf-8 and utf-16 for this use case
0
0
0
0