andreoss

@victornoel `Constant` (as many `Scalar` implementations) is troublesome to use without calling `value()`. I expect that two identical constants should be equal at least. `toString` simplifies logging, as I primarily...

@victornoel Proposal is to extract from this class 1) `Prepended` 2) `Appended` and remove vararg ctor

@victornoel I don't think so. After erasurej `Joined(Iterable)` and `Joined(Iterable

@victornoel Yes, the problem is compile time only. I wanted to suggest to remove vararg ctor, or move it to another class. But if wildcard solves that, it's fine. WIll...

@fabriciofx 1) Using `AtomicReference` in `Cycled` seems to be a poor choice, `Queue` would be a better fit. Same goes for `Repeated` and `Joined`. (Probably `Cycled` should be constructed from...

@fabriciofx Overloaded ctors would be ambiguous 1. `IterableOf(Scalar)` could be as well `Iterable` 2. `ScalarOf(Iterbale)` could be `Scalar`

@victornoel I believe `ScalarOfIterable` should work only on single-element `Iterable`, thowring `NoSuchElement` and `IllegalArgumentExeception` otherwise. Scalar which iterates over `Iterable` doesn't make much sense

@victornoel We can think that `Output` is a medium, and `Text` prints itself to it. It seems to be common in takes for an object to have two methods for...

@paulodamaso Take a look, please

@SimonHarmonicMinor This would go against the principles described here [1] [2]. Since the only good reason for catching is to re-throw, the concrete type of exception is not important. For...