Open HardlyDifficult opened 1 year ago
I think this makes a lot of sense because all library functions can use msg.value
.
Thanks for the fast turn around - that change worked great.
I realize now though that this applies to internal functions as well. Same problem where they cannot be payable in code, but can work with msg.value.
Could we make the exposed library functions payable?
I have an internal library function that considers msg.value, the library function itself cannot by payable (and it wouldn't be require). But to test this library call, I need to be able to pass value. It seems like it would be okay to make all exposed library calls payable so that tests have the option of specifying a value.
e.g. current output:
Desired:
Just started toying around with this plugin, seems super useful - thanks!