It’s not just documentation – here’s a list for the IntelliJ Scala plugin (so far):
- SCL-19928 Heuristics for transparent term aliases
- SCL-19929 An option to navigate to an alias target directly
- SCL-19930 Quick Documentation / Definition: handle transparent aliases
- SCL-19932 Find Usages: support type and term aliases (in both directions)
- SCL-19933 Highlight aliases in the same way as targets
- SCL-19934 Optimize import: take aliases into account
- SCL-19935 Read the RHS of constant val definitions (from .class & .tasty)
All this stems from the semantics – the pattern with two aliases was supposed to be just another way to import things by default, but it’s very different from import as far as IDE is concerned (e.g. if you navigate to an imported name, you navigate to the definition, not to the import statement). If we had some standard way to define a “transparent export”, that would fix these issues automagically.
Of course we can (and will) try to work around this at the IDE side, but it would be great to also address that at the language side, if possible.