That's the compatibility-breaking part. Doesn't mean the replacement function or object can't have the same name, purpose, time complexity, etc. You could pote

That's the compatibility-breaking part. Doesn't mean the replacement function or object can't have the same name, purpose, time complexity, etc. You could potentially even continue to support the existing ones but regard them as unsafe and have the compiler warn if they're used.