Following from the discussion here: https://discourse.julialang.org/t/remove-agent-from-space-but-not-scheduler/127842/10
The summary is: there are good reasons for users to be able to directly add or remove agents to a space, without removing them from existence (the ABM itself) alltogether.
To do this we need to make the add/remove_agent_from_space! public, and also:
- In its docstring document that this function is already called internally in
add_agent! or remove_agent! and therefore does nto have to be manually called by the user if they are doing this operation.
- Test EXTENSIVELY in ALL SPACES whether using these functions directly without
add/remove_agent! leads to any breakages.
This feature is a pre-requisitive step for #910 .
Following from the discussion here: https://discourse.julialang.org/t/remove-agent-from-space-but-not-scheduler/127842/10
The summary is: there are good reasons for users to be able to directly add or remove agents to a space, without removing them from existence (the ABM itself) alltogether.
To do this we need to make the
add/remove_agent_from_space!public, and also:add_agent!orremove_agent!and therefore does nto have to be manually called by the user if they are doing this operation.add/remove_agent!leads to any breakages.This feature is a pre-requisitive step for #910 .