-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In cross-call contract, ink! cannot pass compile for the parent contract contains event #1000
Comments
Same issue. |
Yes it will |
This was referenced Apr 14, 2023
Closed
5 tasks
I am having the same issue. Any idea how to go around it? I am using ink version 4.2.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Questions
It's a bug in ink!, it may appear after pr #665
FAQ
ink! version: e8d4739
cargo-contract version: cargo-contract 0.15.0-unknown-x86_64-linux-gnu
Describe the bug
example repo:
https://github.com/atenjin/ink-event-bug
in this repo, test2 contract crate depends on test contract crate. So the contract
Test2
in test2 will use theTestRef
from the contractTest
in test.and in test/lib.rs:L20, I add a event definition, and do nothing.
and in test2/lib.rs:L23, I aslo define a event:
and emit this event in following code, line 50
then in test2 directory, execute compile command, it cannot pass compile for the following error:
if remove the
emit_event
, thenTest2
can pass the compilation. But we need the event.And If I remove the event definition in
Test
, then compilingTest2
can work normally.and other people so in element, if I change the emit_event like this, can pass the compilation.
Obviously, the type inference is broken when Test2 use the contract TestRef.
I think it can be fixed just changing some small part, right? @Robbepop
The text was updated successfully, but these errors were encountered: