Support arrays as service return types about nexus HOT 3 CLOSED

Meh. If I support String[] then I have to support boolean[], char[], short[], int[], float[] and double[], and due to the inability to use reflection in Nexus, that means I have to write and maintain a ton of boilerplate code to handle each of those array types.

Arrays are "discouraged" in this day and age anyway, why not use RFuture<List<String>> getNames ()?

from nexus.

I see that I had the array variants in Streamable commented out for a while with "Not sure if I want these yet", but then I relented and put them in. Perhaps I should have been sterner in my judgement there and not let that cat out of the bag...

from nexus.

Oh, I guess I use those in generated streamers when the associated Streamable type has a final array field. "Effectively" final arrays is a pretty reasonable thing, so I guess that door is going to be open whether I like it or not. Sigh. I'll add streamers for the array types.

from nexus.