Radosław Waśko

This issue still persist to this day. Updated repro: create a project with following 4 files: `Mod.enso`: ``` type My_Typ Value x ``` `F1.enso`: ``` import project.Mod.My_Typ My_Typ.foo self =...

Related problem - it is possible to define an extension method on a type that already has a method with that name. In such case, the extension method simply seems...

Interestingly, if 2 extension methods are defined _in a single module_, we _do get_ an error: ``` from Standard.Base import all import project.Mod.My_Typ My_Typ.foo self = self.x+2 My_Typ.foo self =...

> Let's change all the constructors in our stdlib codebase that use `##PRIVATE` doc tag to use the proper `private` keyword and ensure that they are checked for private access...

I think it may be worth to add a bit more detail how these methods are supposed to work. I assume the idea is that they will check their caller...

The `null(Internal)` frame also looks a little bit suspicious.

This behavior has caused many headaches for me and my friends working on the DSE Homeworks and it took a long time to track down to exactly this issue -...

I guess one way to deal with such situations is by implementing #5430 or #5431

I've already adapted our data link tests to create the datalinks themelves... but I forgot it's not yet possible: ```diff Index: test/Base_Tests/data/datalinks/example-enso-file.datalink IDEA additional info: Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP UTF-8 =================================================================== diff...

I guess ideally there should also be an easy way to open the Warnings visualization. Could clicking on the warnings icon switch to this visualization? (I guess this may need...