2018-02-19 7:35 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2018-02-18, Gintautas Grigelionis wrote: > > > 2018-02-18 20:30 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > > >> On 2018-02-18, Gintautas Grigelionis wrote: > > >>> - https://github.com/apache/ant-ivy/pull/63 (has to do with choice > of > >>> generics, with are not set in stone yet); > > >> changes the generic type of an argument of a public method inside a > >> public class. > > > That's obvious. Any suggestions? > > I'm not familiar with the Ivy code base so all I can suggest is along > general lines of "think about a different approach" and "document the > break of backwards compatibility if unavoidable". > > This case is specifically tricky as you will only run into problems at > runtime (unless you recompile your code) thanks to type erasure. > Existing compiled code that invokes doesCallersExclude with a Stack of > ModuleRevisionIds will be allowed to call the method. >
Hmmm, I may use (Array)Deque and provide Stack for backwards compatibility, how about that? Gintas
