Contracts with `toString()` functions panic when deployed

Describe the bug ethers fails to deploy contracts with a toString() function. (I was developing a library, but I assume normal contracts have the same issue). There are probably other function names that conflict with native js functions. valueOf() is likely another one.

Reproduction steps Create a contract with a toString() function

library MyLibrary {
    function toString(uint256 value) public returns(string){
        // ...
    }
}

Then, attempting to deploy that contract using ethers and hardhat…

const myLibFactory = await ethers.getContractFactory('MyLibrary')
const myLib = await myLibFactory.deploy() // errors

yields this error message:

TypeError: uniqueNames[name_1].push is not a function
at /.../@ethersproject/contracts/src.ts/index.ts:717:35

Environment: Hardhat 2.4.1, ethers 5.4.6

[zemse]

Can be reproduced with

new ethers.Contract(
  '0x0000000000000000000000000000000000000000', 
  ['function toString() external']
)

[RyanRHall]

Closing, as this seems to be fixed in 5.5.X. Thank you @ricmoo.