Paweł Marks

`*` is not the first suggestion in import autocompletion

1

**To Reproduce** Steps to reproduce the behavior: 1. type `import scala.collection.*` 2. press `Enter` to start a new line The line would be completed with `*#:` which is not what's...

Should be based on branch https://github.com/Kotlin/dokka/tree/f/new_javadoc Example: https://docs.oracle.com/en/java/javase/14/docs/api/java.base/java/lang/class-use/ClassLoader.html

Extension rendering tests

1

The goal of this task is to create tests that check if all required extensions of type are properly rendered for different kinds of types.

Information about typealiases used in signatures should be preserved and available for the user.

1

Right now, dokka is displaying types in signatures how the compiler sees them, so all type aliases are expanded to the real types. It may be unintuitive behavior for many...

**Version(s)** `0.1.12` **Describe the bug** `//> using option "--explain"` doesn't change the compilation output. Probably it has the same root cause as #1023. The problem goes away if we run...

### Switch development from 3.4.1 to 3.4.2 - [x] Create branch `release-3.4.1` from `main` - [x] On `main` in `Build.scala`: Set `baseVersion` to `3.4.2`: - https://github.com/lampepfl/dotty/pull/19683 ### Publish 3.4.0 artifacts...

Re-merge binary literals

8

Binary literals PR should be re-merged in time for 3.5 release. https://github.com/lampepfl/dotty/pull/19405

### Publish 3.3.2 artifacts to Maven Central via CI: - [x] On `release-3.3.2` branch: - [x] In `Build.scala`: Set `baseVersion` to `3.3.2` - [x] In `Build.scala`: Set `referenceVersion` to `3.3.1`...

Before the 1.3.50 release I've realised that some of intentions and refactorings are producing incorrect results when run on files with `\r\n` line endings. They were transforming correct code into...