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
Copy file name to clipboardExpand all lines: program-analysis/echidna/advanced/working-with-libraries.md
-13Lines changed: 0 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,19 +60,6 @@ We can use the coverage report to verify that function using the library (`getBa
60
60
30 | | }
61
61
```
62
62
63
-
However, the code of the library itself will not have their coverage displayed correctly:
64
-
65
-
```
66
-
6 | | library ConvertLib{
67
-
7 | | function convert(uint amount, uint conversionRate) public pure returns (uint convertedAmount)
68
-
8 | | {
69
-
9 | | return amount * conversionRate;
70
-
10 | | }
71
-
11 | | }
72
-
```
73
-
74
-
This is caused by the usage of `delegatecall` to execute contract code and [unfortunately we do not have a workaround for it right now](https://github.com/crytic/echidna/issues/1042).
75
-
76
63
## Summary
77
64
78
65
Working with libraries in Echidna is supported. It involves to deploy the library to a particular address using `deployContracts` and then asking `crytic-compile` to link the bytecode with the same address using `--compile-libraries` command line.
0 commit comments