After refactoring some files, we found out that there is one unused method in code, but we cannot remove it since, We don't want to break binary compatibilty.
it's hard to answer without more context - like what programming language is involved, etc. If you're writing a library where there is a separate client component, and people may be using older versions of the client with newer versions of the library, it may be important to maintain backward compatibility. I'm not sure what the situation is here, but my impression is that it should be okay to remove the unused method.
We're a place where coders share, stay up-to-date and grow their careers.
Top comments (1)
it's hard to answer without more context - like what programming language is involved, etc. If you're writing a library where there is a separate client component, and people may be using older versions of the client with newer versions of the library, it may be important to maintain backward compatibility. I'm not sure what the situation is here, but my impression is that it should be okay to remove the unused method.