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.
For further actions, you may consider blocking this person and/or reporting abuse
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.
For further actions, you may consider blocking this person and/or reporting abuse
100% open-source tool-use platform (backend, dev portal, integration library, SDK/MCP) that connects your AI agents to 600+ tools with multi-tenant auth, granular permissions, and access through direct function calling or a unified MCP server.
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.