Hubert Plociniczak ae0889e843 Make ArrayOverBuffer behave like an Array/Array.sort no longer mutates the Array (#4022) ... Most of the problems with accessing `ArrayOverBuffer` have been resolved by using `CoerceArrayNode` (https://github.com/enso-org/enso/pull/3817). In `Array.sort` we still however specialized on Array which wasn't compatible with `ArrayOverBuffer`. Similarly sorting JS or Python arrays wouldn't work. Added a specialization to `Array.sort` to deal with that case. A generic specialization (with `hasArrayElements`) not only handles `ArrayOverBuffer` but also polyglot arrays coming from JS or Python. We could have an additional specialization for `ArrayOverBuffer` only (removed in the last commit) that returns `ArrayOverBuffer` rather than `Array` although that adds additional complexity which so far is unnecessary. Also fixed an example in `Array.enso` by providing a default argument.		2023-01-09 17:49:49 +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	Make ArrayOverBuffer behave like an Array/Array.sort no longer mutates the Array (#4022)	2023-01-09 17:49:49 +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