Jean-Baptiste G.
Jean-Baptiste G.
@gneuvill the return type is unfortunately not taken into account by javac when checking for erased method clash. What do you think of ``` java static SData.Add1 getAdd1(Seminar temp) {}...
@AndreasVoellmy thank-you very much for investigating this. I will have a look shortly at what can be optimized, there is certainly ways to improve that time. ps: some past release...
@AndreasVoellmy It looks like maven does not recompile sources in `generated-sources` when using the `-proc:none` flag. If I move the generated sources into `src/main/java` I get back the long compile...
I just meant using `mvn compile` instead of `mvn clean compile`. Then the annotation processor only process classes that have been modified since last compile.
Right, I forgot that I wanted to try out expliciting type args in generated code. Let's see what this brings.
Slightly improved via the last commits: see https://github.com/derive4j/derive4j/blob/master/examples/src/main/java/org/derive4j/example/ArrayWrapper.java#L21 But yeah, not sure if it's worth going any further: one should probably use immutable array wrappers anyway.
The main constraint is that everything that is generated must be type-safe. `C1` is an open hierarchy so there is no static guarentees that the subclasses of `C1` generated by...
The issue is that all sound instances of C1 should be comparable, be it generated by derive4j or manually crafted. Ie. ```java boolean testEqualsWithManuallyDefined() { return C1s.m1(1).equals(new C1() { public...
Looks like `String name1, String name2, String name3, String name4, Integer age, String adress` should go into its own product type, no?
I think I got an idea for this: ```java @Data(flavour = Flavour.FJ) public static abstract class Staff { // a dumb type Staff() {} interface Cases { R Common(String name1,...