Consolidate Vector & Array

[wdanilo]

This task is automatically imported from the old Task Issue Board and it was originally created by jaroslavtulach.
Original issue is here.

---

#183000876 has removed the difference between Enso Array & Vector - they both "duck like a polyglot array". The only difference is that Vector originates from Enso and is idealized as immutable. Array comes from Java, JavaScript, Python, etc. and nobody knows much about it.

The next step is to consolidate them more:

• methods available on Vector and Array shall be the same (as much as possible)
• methods needlessly converting between them can be removed - like Vector.to_array, Vector.unsafe_at
• the Vector.from_polyglot_array method shall be renamed - see discussion

Tasks:

• Write a test that compares methods available on Vector and Array type
• Make sure the same methods are available in both types
• Make sure Vector and polyglot array can be used interchangeably when calling builtins

Deferred Tasks

• Remove methods that make no sense anymore (likely Vector.to_array)
• Find better name for Vector.from_polyglot_array
• Benchmark using at instead of unsafe_at and if fine, remove unsafe_at
• Remove needless conversions to Vector - like (Vector.from_array arr) . map

Blockers:

#183000876 resolved
#183266964 resolved
#183058716 resolved
#184278959 resolved

Comments:

To consolidate Vector & Array we want to make sure both Vector and Array can be used interchangeably. That's not currently the case. There are two known problems where explicit convertsion to_array is still required:

• #183266964
• #183058716

I am afraid we have to address these two sample needless conversions in builtins before we can claim a victory in consolidating Vector & Array.
(jaroslavtulach - Sep 29, 2022)

---

**Hubert Plociniczak** reports a new **STANDUP** for yesterday (2023-01-09):

Progress: QA, trying to work on consolidation but little work done due to other distractions. Investigated double reporting of errors as noticed by Radek (will report the ticket once I have something tangible). It should be finished by 2023-01-12.

Next Day: Next day I will be working on the #183217534 task. More QA and consolidation work. (Enso Bot - Jan 10, 2023)

---

**Hubert Plociniczak** reports a new **STANDUP** for yesterday (2023-01-11):

Progress: QA, problems with Windows setup to reproduce vcs issues. Minor tweaks to consolidation work (decided to postpone until James' work on API improvements lands. It should be finished by 2023-01-12.

Next Day: Next day I will be working on the #183217534 task. Look into resolving fully qualified names, pick up vector/array work. (Enso Bot - Jan 12, 2023)

---

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2023-04-06):

Progress: - Consolidate Array and Vector: #6218

• review "batch insert": Batch insert suggestions #6189
• processing emails & discussions
• book club
• rename bug reported: Renaming a project silently fails with no explanation #6214
• prototype of sqrt: Numbers.sqrt & co. are slow - benchmark first #6175 (comment) It should be finished by 2023-04-11.

Next Day: Easter vacation

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2023-04-11):

Progress: - Array&Vector PR merged: #6218

• static vs. instance discussion: https://github.com/orgs/enso-org/discussions/6216#discussioncomment-5576325
• review: Add Warning methods onto Any to make working with them easier. #6176 (review)
• review: Language Server support for execution environments #6217
• review play button protocol: https://github.com/enso-org/enso/pull/6217/files#r1163038831
• Map literal syntax via stdlib: https://github.com/orgs/enso-org/discussions/6167#discussioncomment-5581090 It should be finished by 2023-04-11.

Next Day: 5x slower if cascade

GitHub

Static-oriented syntax for invoking instance methods vs Simple static methods · enso-org · Discussion #6216

The context The PR #3764 introduced a calling convention that allows to write Foo.method (Mk_Foo 123) as a synonym of (Mk_Foo 123).method (just to note, the status of the static/instance calls befo...

GitHub

Language Server support for execution environments by 4e6 · Pull Request #6217 · enso-org/enso

Pull Request Description

close #6133
Changelog:

add: executionContext/setExecutionEnvironment request
update: executionContext/recompute request to have optional executionEnvironment parameter.

...

GitHub

Literal format for the Map type · enso-org · Discussion #6167

As we now have a built-in Map type we would like to add a literal format to create a map instance. There appears to have been old support within the old parser for a syntax: enso/engine/runtime/src...