Michał Pałka

But is the way how types are printed in REPL the only problem or do the two cases you mentioned have some real impact on evaluation of code?

Actually for @b-studios' example I would find the `A ?=>` overload the right choice because if `B` already given in scope, you don't need to require an additional parameter to...

In case of ``` given B(1) withB { println(summon[B]) } ``` it is quite explicit that `summon[B]` should use the given instance provided by the method and not the one...

According to the bisect script: ``` Last good release: 3.3.0-RC1-bin-20230115-ed5b119-NIGHTLY First bad release: 3.3.0-RC1-bin-20230116-d99d9bf-NIGHTLY bisect found first bad commitPrevious HEAD position was 49df37931f Use tree checker for macro expanded trees...

It looks like the problem is that the limit of characters used for truncation got raised from 1000 to 50000. I think we should make the default 1000 again (3000...

Oh, right, the fact that printed string literals are trying to be highlighted like code seems to be the core problem here

To make things clear: named exports from packages do work - only wildcard exports don't. I assume that's because of complications wildcard imports from packages would bring to incremental compilation....

I would say it's not only about longer compilation times but also about correctness of code, unless we give up incremental compilation and compile everything from scratch each time, which...

To make things clear it should be noted that: * singleton types (like `this.type`) are distinct from non-singleton types - so e.g. ```scala val x: Tuple = (1, 2, 3)...

@nightscape thanks for your contribution! I'm afraid your changes can't be incorporated into the main branch at the moment because of the reasons mentioned in the comments but I'll try...