Isolates cannot be used as a sub-namespace within a project
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- distributed-systems
Research direction
Start by reviewing the references to #.isolate mentioned in the issue and compare the scope with related issue #31. Identify how the isolate functions currently depend on #.isolate and confirm that the intended result is an isolate namespace that works as a sub-namespace within a project.
Written by the indexing model from the issue text.
Description
Related to #31 I think
Says @rikedyp who opened the original mantis issue (21523):
Isolate functions refer to #.isolate, and therefore are not portable within a project. This can be worked around by having #.⎕CY'isolate', or by modifying the functions, but it would be nicer to have all of the functions inside their own "isolate" namespace, rather than #.II, for example.
Indeed there are a lot of references to #.isolate
Certainly still true in Version 1.6 (2025-12-23 12:47:08 -0500) built at 2026-01-26 20:20:30, but originally reported in earlier versions.
This seems to have quite a lot in common iwht #31.
- Dominant language
- APL
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Dyalog/isolate
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
On Linux (?all non-Windows platforms?) attempting to run an isolate with child devt interpreters generate a FUTURE ERROR: 1119:May be free again @mkromberg claimed this 242 days ago, and no pull request is open. Open
-
Make isolate.ynys.getDRC also look for #.CongaMay be free again @bpbecker claimed this 409 days ago, and no pull request is open. Openenhancement
-
Allow remote processes to connect back to "parent" processMay be free again @bpbecker claimed this 636 days ago, and no pull request is open. Openenhancement
-
isolate only works if isolate is copied into #May be free again @bpbecker claimed this 1001 days ago, and no pull request is open. Open
Similar issues
-
bug p0-mandatory
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Text::diff_range panics when the snapshot's delete set names a client the document has not seenPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kind/bug require/backport require/qa-review-coverage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
longhorn/longhorn#14228 · 2 reactions ·
Maintainers usually reply within 1 day
-
defect
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[Enhancement] ControllerClosure request-completion semantics lack direct testsPossibly taken @chennaji9 claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/rocketmq#11337 · 1 comment ·
Maintainers usually reply within 1 day