Josef Pfleger
Josef Pfleger
I don't mean to interrupt your discussion but I want to point out that this PR is not about whether JSON is good or bad on the event bus. It...
@vietj roger : )
Hm, but since `JsonObject` and `JsonArray` use `Map` and `List` internally, "free cast" is really all around us already anyways. Consider: arr.add("foo"); arr.getInteger(0); // ClassCastException Not sure how that is...
I don't think there are any compatibility issues. Because of type erasure in Java, the method signature in bytecode will stay the same and everyone using `stream()` can continue to...
Any more thoughts on accepting (or rejecting) this PR? I still think this is very useful.
Interesting. You mean `JsonArray` will *implement* `List`? Or *extend* `ArrayList` or similar? And will `JsonObject` implement `Map` then accordingly?
Had a look at the 4.0 features. I don't think there is an overlap with my suggestion. I still find this PR useful.
With 4.0.0.CR1 released, I still think this PR is a good idea, very useful, and without any backward compatibility issues. Please let me know if you have any other concerns/questions...
Absolutely, the same way the other methods currently throw `ClassCastException`s: ``` arr.add("foo"); arr.getInteger(0); // ClassCastException ``` (also see discussion above). This PR doesn't change the way `stream()` (or `stream()`) behaves...
Yes, we've had such little helpers in our projects for years now (check the date of this PR), also because we use rxjava heavily. This would allow us to get...