passing ls:let down through multiple levels
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 20
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
from our paper:
Importantly, ls:let exists in the context of a parent. This means that the value of a ls:let cannot be passed down through grand children without having to use ls:let again. I.e.
ls:let num-turtles count turtles
ls:ask 0 [
ls:ask 0 [
create-turtles num-turtles ;; WILL ERROR
]
]
Rather, the modeler would need to ask its child model to re-assign the ls:let in its own context, and then pass that into its own child model – the grandchild of the original model:
ls:let num-turtles count turtles
ls:ask 0 [
ls:let child-num-turtles num-turtles
ls:ask 0 [
create-turtles child-num-turtles
]
]
Any way around this?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by tracing how LevelSpace handles ls:let bindings across nested ls:ask contexts. Use the examples in the issue as the behavioral cases: determine whether a value can reach a grandchild without reassignment, and document or test the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100