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
After reading #14501, I believe the case I am describing is not well-expected behavior.
When including a library Lib (with using-for) into another library Lib2, events from Lib are missing in Lib2 ABI. However, when I do the same with a contract, i.e. include Lib into contract Foo, the contract's ABI includes events from Lib.
Note that Lib2 may be deployed as a standalone lib and delegatecalled into, making it impossible to resolve the emitted event correctly.
Environment
Compiler version: 0.8.28, 0.8.0, 0.7.0
Compilation pipeline (legacy, IR, EOF): legacy, IR
Description
After reading #14501, I believe the case I am describing is not well-expected behavior.
When including a library
Lib
(withusing-for
) into another libraryLib2
, events fromLib
are missing inLib2
ABI. However, when I do the same with a contract, i.e. includeLib
into contractFoo
, the contract's ABI includes events fromLib
.Note that
Lib2
may be deployed as a standalone lib and delegatecalled into, making it impossible to resolve the emitted event correctly.Environment
Steps to Reproduce
Compile and print ABI
The text was updated successfully, but these errors were encountered: