Hubert Plociniczak 20c22f2422 from/all import must not include module in name resolution (#3931) ... It appears that when were doing `from XYZ import all` the module `XYZ` was also being taken into account during name resolution. This was unfortunate and became problematic when one had a type with the same name defined in it. During pattern matching one could not simply do ``` from XYZ import all ... case ... of _ : XYZ -> ... ``` since the compiler would complain that we try to pattern match on a type but give it a module. The module is now excluded from the name resolution, when importing everything from the module. It appears that this "feature" was used in a number of our tests, so they had to be adapted. This fixes task 4 in https://www.pivotaltracker.com/story/show/183833055		2022-11-30 16:28:57 +00:00
..
bin	Enso Integration with Ideal Graph Visualizer (#3533)	2022-06-23 04:43:49 +00:00
engine/THIRD-PARTY	Project save backed by git (#3851)	2022-11-14 17:32:39 +00:00
launcher	Load the File_Format types via a ServiceLoader (#3813)	2022-10-24 09:55:18 +00:00
lib/Standard	from/all import must not include module in name resolution (#3931)	2022-11-30 16:28:57 +00:00
project-manager/THIRD-PARTY	Load the File_Format types via a ServiceLoader (#3813)	2022-10-24 09:55:18 +00:00
enso.bundle.template	Better component handling in the project manager (#1399)	2021-01-15 15:26:51 +00:00
launcher-manifest.yaml	Bump the development version number (#1389)	2021-01-06 08:57:02 +00:00
manifest.template.yaml	Bump Minimal PM/Launcher Versions for New Engine (#1854)	2021-07-13 13:08:00 +02:00