Currently, when e.g an interface and a superinterface override each others methods, they are collected twice. However, this then crashes on duplicate map entries when converting to a mapbacked (using immutable map).... ... We could either simply make it ignoring it (by using another map , not the immutableMap builder), or throw, when scanning the methods, to avoid such constructs.....
Currently, when e.g an interface and a superinterface override each others methods, they are collected twice. However, this then crashes on duplicate map entries when converting to a mapbacked (using immutable map).... ... We could either simply make it ignoring it (by using another map , not the immutableMap builder), or throw, when scanning the methods, to avoid such constructs.....