Anna Shaleva
Anna Shaleva
This problem is more complicated than it seems to be. > is this intended? Yes, it is intended, because our compiler generates DebugInfo according to [NEP-19](https://github.com/neo-project/proposals/blob/master/nep-19.mediawiki) standard. And here what...
I thought about it, but ideally we need to generate coverage using only debug info specification, and debug info itself is strictly fixed by the standard.
> We know function boundaries. The problem is that right now in general case we don't. For package-level function declarations we can exclude some instructions from coverage calculations based on...
> Shouldn't it be a separate https://github.com/neo-project/proposals/blob/master/nep-19.mediawiki#user-content-Method? It's a contravercial question, because it's not a fully-qualified private or public method of the contract; it's an anonymous function. And our debug...
> You've probably seen some func_name.1.1 A good example, ref. https://github.com/nspcc-dev/neo-go/issues/3619.
`RET`-related problem will be fixed by https://github.com/nspcc-dev/neo-go/issues/3622. The remaining problems with smaller overlapping blocks should be fixed on the coverage side, but this problem is not that critical and may...
@AliceInHunterland, please update the container IDs.
@AliceInHunterland, ready for review?
> Let me check https://github.com/nspcc-dev/neo-go/issues/3668 first? I think that we won't change container IDs one more time, hence we can merge this PR and then use ready-to-use config files to...
Depends on https://github.com/nspcc-dev/neo-go/pull/3554.