Should we just go ahead and use SVector
in position and velocity fields of ContinuousSpace...?
#672
Labels
continuous
Continuous space related
discussion
quality of life
QoL enhancements that make user experience smoother
Alright, so, plenty of times in many use cases of
ContinuousSpace
, it becomes an obvious pain to useNTuple
instead ofSVector
. So, should we just go ahead and change the types to static vectors? Problem is, I am not sure how breaking this is. Unless a user for whatever reason annotatted the position type, everything the user did before will work now as well. This includes changing velocity via a tuple,agent.vel = (1, 2)
would still work even ifvel isa SVector
.For example, this problem came when making the Flocking example, in the discussion in #671 , in the integration example with CellListMap.jl, the bacteria example, I mean, practically everywhere with
ContinuousSpace
.The text was updated successfully, but these errors were encountered: