Closed akinsho closed 5 years ago
I'm probably missing some information here to answer correctly, but looking at the code, maybe a naive implementation could be to loop over CamomileLibraryDefault.Camomile.(UChar.code(UTF8.get(str, 0)))
multiple times for larger digits?
It seems a bit weird to get batteries only for this kind of thing?
Also, if parsing is needed, maybe having a look at https://github.com/inhabitedtype/angstrom could be helpful as well?
@tcoopman that's a good idea, haven't tried that yet was futzing with using the length
or last
methods. Yeah batteries is an excessive solution, I only mentioned it in case it might be the sort of thing we'd use for other reasons my oversimplification is that it has a lot of utilities we might want anyway but it definitely isn't the first thing I was planning to try
@Akin909 If you look at batteries for somethings, I think having a look at core would also be good.
This is no longer an issue with the libvim
work, as we no longer have the Msgpck transport layer - we get these ids directly as integers / pointer references.
Neovim returns a custom
ExtType
fromMsgPck
when we receive or requestwindow
,buffer
ortab
information, currently we convert this usingCamomile
inUtility.re
however the parsing atm only works for single digits, so will need to be revisited so it can parse larger digitsOptions I've found