Alex Kladov

I've tried to implement my design: https://users.rust-lang.org/t/tom-yet-another-format-preserving-toml-parser/18765. Overall, it seems to work, and I am quite happy with the fact that it allows both lossless parsing as well as lossless...

Consider https://github.com/blyxxyz/lexopt as well it is "more correct" across some dimensions, while being similarly lean.

We are hitting this in rust-analyzer: https://github.com/rust-analyzer/rust-analyzer/issues/4263#issuecomment-762800167. Out of curiosity, how hard would it be for Emacs to report offsets in ut8 coordinate space (I believe Emacs uses that internally)?...

@nbfalcon thanks, I didn't realize that the extension already exists. I actually would prefer to fix this on the server-side than, to create social pressure to actually officially adopt that...

On rust-analyzer's side, we fully implemented clangd's extension for UTF-8 offsets, so, on Emacs side you an either: * do utf-16 translation, which needs some code and CPU time *...

Yeah, I think I could use an API like `Sink` and `Stream` traits from futures 0.3 with crossbeam channel. Basically, wrap both `Sender` and `Receiver` into traits which provide monadic...

Aha, this matches my thoughts after poking at the code for 10 minutes! #1505 looks really sweet for this and other reasons, huge fan of that direction! I guess this...

I am seeing the same effect, but looks like the root cause might be different. Seems filters with value somehow don't enable spans? Ie, if I have a single filter,...

Still very much a problem I believe! I've submitted a reproducible test here: https://github.com/tokio-rs/tracing/pull/2199. I can potentially work on a fix, but, a) no promises :), and, b) I would...

Although, taking a step back here: The reason why we were hitting stack overflows is because we had buggy code which created infinitedely deep span trees. The bug was similar...