Hi Chia-Ping, Sorry for the delay on this. One thought though: looking at current implementations on github they seemed a bit elaborate, which makes me think that people don't usually want to use it as a lambda. But since in your KIP you added it, what was your use case there?
"Q: Which implementation is suitable for serialize()/deserialize()? maybe just throw exception?" For now I think l it'll be useful to not throw exceptions but I have to check if there is a use case for this. Do you have any use cases btw? :) Viktor On Tue, Jul 31, 2018 at 12:24 PM Chia-Ping Tsai <chia7...@apache.org> wrote: > Bumping up! > > On 2018/07/09 08:50:07, Viktor Somogyi <viktorsomo...@gmail.com> wrote: > > Hi folks, > > > > I've published KIP-336 which is about consolidating the > > Serializer/Deserializer interfaces. > > > > Basically the story here is when ExtendedSerializer and > > ExtendedDeserializer were added we still supported Java 7 and therefore > had > > to use compatible constructs which now seem unnecessary since we dropped > > support for Java 7. Now in this KIP I propose a way to deprecate those > > patterns: > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=87298242 > > > > I'd be happy to receive some feedback about the KIP I published. > > > > Cheers, > > Viktor > > >
