Justin M. Keyes

3c401125f83529c4ec52c6e89f201e9d4650030e looks much better. I was really wondering why all that code was needed for this feature...

> The meta structures are useful to communicate to a user that a function is deprecated (with `@deprecated`) with an optional message of when. I will consider adding the signatures...

> how it allows more experimentation? Reducing the cost of potential deprecations reduces friction for introducing (some classes of) new interfaces in the first place.

> The usual cost of deprecations is the ongoing maintenance of said deprecated functions. Like I said I'm working on a proposal that eliminates that problem. The cost of deprecations...

> This change introduces a high cost to users who will lack the documentation required to migrate code. It introduces some cost there, but the docs are still available in...

We can make this conditional on the api-level where a function was deprecated. For example in this very PR, notice how 20-year-old vimscript functions are in the meta info. Those...

> There is no "buying time" here. I don't know why you just declare that. There obviously is. I have made the point over and over that programmatic compat can...

> nvim just takes what the lsp gives it as is Yes. There is no "issue" here except that the hover window is too narrow (that depends on the "parent"...

> Is there anything I should be particularly careful about? In terms of implementation, my first thought is that instead of special-casing `` as in the current implementation, we should:...

> For example in IPython when you start with `def hello():` it automatically knows that you want to enter multiline mode and it also indents your next prompt. That might...