Jan Kwakkel

I think my main objection is not to time attribute perse but to the use of time and step as optional keyword arguments to model.step. This is a new feature,...

> Fun fact: I have a DEVS model in development right now where a steps counter would be very useful, since I still have a model step and want to...

> I think at this point we disagree on a philosophical level what a simulation library should offer. My last question was really about trying to understand the issue. So...

> Let me be perfectly clear: It's 100% optional. No it is not. `step` and `time` are now reserved keyword arguments used by `Model.step`. Sorry to be annoying about this....

>What I meant with philosophical differences, is that I think [convention over configuration](https://en.wikipedia.org/wiki/Convention_over_configuration) is in general a good principle for Mesa to follow. Why? Because it offers two things that...

> Loops might still be nice if you want to create complicated agents and positon them etc, but an elegant alternative should be present in the AgentSet or model for...

> Thanks for taking a shot as this, I’m intrigued why it increases code complexity in the examples instead of decreases it. Probably because of the lists that need to...

I have updated the code a little bit. You can now pass either a sequence of length n (i.e., the number of agents to create) or any other object as...

I updated the benchmarks to use `self.rgn`. This cleans up the number of lines of code a bit and is quite convenient. The current implementation needs further refinement. I check...

I have picked this up again, and it's ready for a review. It now supports `list`, `numpy array`, and `tuples`. Since the code relies on checking whether the length of...