Potential breaking changes

[LourensVeen]

Here's a list of some possible improvements that will change the API. We're still at version 0, so that's legal, and the sooner the better, but are they worth it?

• ymmsl.ParameterValue should now be SettingValue, got missed in the rename.
• allow more than one dimension more or less between compute elements, and have receive-on-any-slot as the only receive method for vector/array ports
  • sending would still require getting sizes, and it's a ragged array, so that's still tricky to get right
  • any deadlock issues with this?
  • any other way of implementing a shared surrogate proxy in front of a 2D set of instances?

[LourensVeen]

The first item was done in 0.2.0, the second one would actually probably extend the API, not modify it.