Open 0xicingdeath opened 7 months ago
The coverage html output doesn't seem to support full unicode output
If the following is in the contracts:
/*´:°•.°+.*•´.*:˚.°*.˚•´.°:°•.°•.*•´.*:˚.°*.˚•´.°:°•.°+.*•´.*:*/ /* XXXXXXXXXXXXXXXXXXX */ /*.•°:°.´+˚.*°.˚:*.´•*.+°.•°:´*.´•*.•°.•°:°.´:•˚°.*°.˚:*.´+°.•*/
the coverage output turns it into:
391 | | /*´:°•.°+.*•´.*:˚.°*.˚•´.°:°•.°•.*•´.*:˚.°*.˚•´.°:°•.°+.*•´.*:*/ 392 | | /* XXXXXXXXXXXXXXXXXXX */ 393 | | /*.•°:°.´+˚.*°.˚:*.´•*.+°.•°:´*.´•*.•°.•°:°.´:•˚°.*°.˚:*.´+°.•*/ 394 | | 395 | | /// @dev Mints `amount` tokens to `to`, increasing the total supply.
master
No response
It seems that solc fails to produce correct source mapping in these cases, so not a lot we can do. However, this will be documented in secure-contract.com to make users aware.
Describe the issue:
The coverage html output doesn't seem to support full unicode output
Code example to reproduce the issue:
If the following is in the contracts:
the coverage output turns it into:
Version:
master
Relevant log output:
No response