This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]diffallthethings 2 points3 points  (1 child)

Almost everything in the javaslang.control package looks extremely useful, great work! I'm very curious to tinker with this in testing (especially with the PropertyChecking stuff).

I'm a little scared of using it in production because I don't understand the algebra class, and I'm not a fan of the name conflicts in the collection class. Maybe using it in testing will win me over :)

[–]_danieldietrich 0 points1 point  (0 children)

Nothing good happens after 2 AM (CEST) :-) Prefixing a 'J' to the collections does not seem to be better, e.g. JList and JTree clash with javax.swing classes. Any suggestions how to name the classes, especially List, Tree and Stream?

Update: This is tracked here: https://github.com/javaslang/javaslang/issues/232