Skip to content
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

New API for NeoContract: System.Runtime.GetInvocationCounter #307

Closed
erikzhang opened this issue Jul 9, 2018 · 2 comments · Fixed by #813
Closed

New API for NeoContract: System.Runtime.GetInvocationCounter #307

erikzhang opened this issue Jul 9, 2018 · 2 comments · Fixed by #813
Labels
Discussion Initial issue state - proposed but not yet accepted
Milestone

Comments

@erikzhang
Copy link
Member

The invocation counter records the number of times each contract was invoked in current InvocationTransaction.

Consider that we have an InvocationTransaction with the following Script:

APPCALL <A>
APPCALL <B>
APPCALL <B>
APPCALL <C>

If we call System.Runtime.GetInvocationCounter in each contract, we will get:

  • 1 from APPCALL <A>
  • 1 from the first APPCALL <B>
  • 2 from the second APPCALL <B>
  • 1 from APPCALL <C>
@erikzhang erikzhang added the Enhancement Type - Changes that may affect performance, usability or add new features to existing modules. label Jul 9, 2018
@erikzhang erikzhang added this to the NEO 3.0 milestone Jul 9, 2018
@igormcoelho
Copy link
Contributor

Hi guys, what's the use case for this? Anyway, it's always good to have new tools :)

@erikzhang erikzhang added Discussion Initial issue state - proposed but not yet accepted and removed Enhancement Type - Changes that may affect performance, usability or add new features to existing modules. labels Oct 9, 2018
@igormcoelho
Copy link
Contributor

I see this has many potential applications, let's go for it! any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants