You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similarly, the Asian characters in below comments from 0x5d0d76787d9d564061dd23f8209f804a3b8ad2f2_FoMo3Dlong.sol also cause source mapping problems:
struct Round {
uint256 plyr; // pID of player in lead, lead领导吗?
uint256 team; // tID of team in lead
uint256 end; // time ends/ended
bool ended; // has round end function been ran 这个开关值得研究下
uint256 strt; // time round started
uint256 keys; // keys
uint256 eth; // total eth in
uint256 pot; // eth to pot (during round) / final amount paid to winner (after round ends)
uint256 mask; // global mask
uint256 ico; // total eth sent in during ICO phase
uint256 icoGen; // total eth for gen during ICO phase
uint256 icoAvg; // average key price for ICO phase
}
The text was updated successfully, but these errors were encountered:
Certain characters (or scripts) in Solidity comments appear to cause incorrect source mappings.
For example, in
0x06012c8cf97bead5deae237070f9587f8e7a266d_KittyCore.sol
, the symbol that looks like underscore in "email_protected":Similarly, the Asian characters in below comments from
0x5d0d76787d9d564061dd23f8209f804a3b8ad2f2_FoMo3Dlong.sol
also cause source mapping problems:The text was updated successfully, but these errors were encountered: