Dirk Lattermann

See [the test module docs](https://modules.ceylon-lang.org/repo/1/ceylon/test/1.3.3.1/module-doc/api/index.html#assertEquals), so, yes.

Something similar was implemented in #489 (providing a `shared Byte[] readBinary()`.)

I didn't need to process large bodies in binary yet, but I think a streaming way will be useful and a `Byte[]` will be awkward sometimes.

Thanks, @gavinking , for the correction (and your fix, of course!). I strongly suggest adding clarification about the use of type parameter of those methods. It surprises me that `Arguments`...

In the case of smaller/equal/larger being in the language module, they did not yet interfere with my usage for them. But in general, I dislike things in the global namespace...

Would that mean that the "streaming methods" that are usually associated with the notion of streams (like `map`, `filter`, `reduce` etc) should be moved from `Iterable` to `Iterator` aka `Stream`?...

@gavinking well, it's not the standard java @Inject annotation, I should have noted. This one is ```java @Retention(RUNTIME) @Target( { FIELD, PARAMETER }) public @interface Inject ``` (comes from apache...

I agree that the FIELD-targetted annotations should be placed on the field declaration. The question here is if it should also be placed on the parameters (which I would deem...

I tested my similar use case (sealed interface with type parameter used in abstract property). It is working perfectly well with Kotlin 2.2.0-RC! ``` plugins { kotlin("jvm") version "2.2.0-RC" kotlin("plugin.serialization")...