> > Ok. That is true. It works fine for one method, but if you have multiple > methods they have to have separate names like "value2", "values3". So, the > following *is* possible. Whether you want to do it is your choice. > > > public static <T1, T2> Table<Record2<T1, T2>> values2(Collection<? extends > Row2<T1, T2>> rows) > public static <T1, T2, T3> Table<Record3<T1, T2, T3>> values3(Collection<? > extends Row3<T1, T2, T3>> rows) > > There's already a feature request asking for the transformation of Select<R extends Record[N]> into Row[N]<...>: https://github.com/jOOQ/jOOQ/issues/3796
This would be the same, then. Sooner or later, we'd have plenty of API elements where the degree/arity is part of the method name, because of this limitation of the Java language. I'd prefer not to go down this direction, because that would feel even more fishy at the use site. The way it is right now isn't nice. But it's acceptable as it is relevant only to edge cases. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
