<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Just FYI - due to change of plans we decided to postpone this :( The main reason is that we want to have an editor against which we can test the feature first.<div class=""><br class=""></div><div class=""><div class=""><div class="">Jan</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 17, 2019, at 1:05 AM, Sam McCall <<a href="mailto:sammccall@google.com" class="">sammccall@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">On Wed, Jan 16, 2019 at 7:44 PM Jan Korous <<a href="mailto:jkorous@apple.com" class="">jkorous@apple.com</a>> wrote:<br class=""></div><div dir="ltr" class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Our intended use-case is clangd talking to the recently announced SourceKit-LSP service:<br class=""><a href="https://github.com/apple/sourcekit-lsp" class="">https://github.com/apple/sourcekit-lsp</a><br class="">I haven’t really thought about details yet (including how to approach testing) but I assume we’ll have some integration tests in SourceKit-LSP. But it makes sense to test (at least manually) with some editor client too.</blockquote><div class="">Understood - I think a lot of the decisions about details will depend on how this feels in practice in an editor (latency, signal-vs-noise) so I think we'll need it connected to a real editor to really understand. I guess there's a prototype of XCode that can use this, but the rest of us need to find something to try it out on too :-)</div></div><div dir="ltr" class=""><br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class=""><span class="">No, it’s really the server who’s responsible for ignoring these. I guess it makes sense since client can’t just decide to not send 'textDocument/didChange’ to server as they would get out of sync.<br class=""></span><div class=""><a href="https://github.com/Microsoft/vscode-languageserver-node/pull/367/files#diff-0253ecfa5ea7304bd5d168e2665e2fd1R54" target="_blank" class="">https://github.com/Microsoft/vscode-languageserver-node/pull/367/files#diff-0253ecfa5ea7304bd5d168e2665e2fd1R54</a></div></div></blockquote><div class="">Ah right - the server is responsible for deciding when to send a syntax update, and the client is responsible for interpolating in between.</div><div class="">So the server has the responsibility of guessing when the client's interpolation will do a better job and it shouldn't waste time calculating and/or sending a new notification. <br class=""></div></div></div></div>
</div></blockquote></div><br class=""></div></div></div></body></html>