Docstring hover text uses wrong definitions

[atomb]

When generating the langdef document created in this PR, the generated HTML is almost exactly what I'd like to have in a language semantics document, with one caveat. The types and functions that appear in doc strings have hover text, but that text consistently uses the doc string from the wrong definition.

I think this worked correctly with an earlier version of the code, though I unfortunately don't have a commit available for which that's true.

It could be that the way I have this document structured is not a recommended use case, and I'd welcome suggestions of a different way to structure things.

[david-christiansen]

I've been unable to reproduce this. However, I've seen similar behavior before and I suspect I know what's causing it.

Many of the commonly-used simple web servers (like Python's http.server, but also a JS one whose name is escaping me) don't implement caching correctly. If you're reading the document locally, and you rebuild it, then it's sometimes necessary to turn off caching in browser devtools.

Internally, Verso de-duplicates the docstrings used in hovers, assigning each of them an ID. These IDs are mapped to the docstring text in the generated file -verso-docs.json. If your browser doesn't get the modified version, then they can appear out of date.

One workaround for the Python web server library is to turn off caching, as is done here.