Include the reflection rule as a field of a new wall/disk object

[dpsanders]

Currently, to define a new collision rule, e.g. random or "pinball" dynamics, you have to duplicate each wall type and define collision functions with each new type. This leads to a significant amount of code duplication (e.g. RandomWall and RandomDisk objects).

Instead, the suggestion is to include the collision function (specular, random, pinball, etc.) as a parametrised field of each wall object. This should reduce code repetition, with no (?) loss in performance.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Datseris]

This isn't really breaking. One would still like to keep the current Wall and Disk for (a) performance and (b) education (since they are the simplest possible implementations of an obstacle).

One more implementation should be necessary for the suggested type here, which would merge with RandomWall as well. Then, any kind of functionality would be fine.

This is an easy issue, given the amount of tutorials we have on "defining your own obstacle".