Skip to content

Skip coverage for methods generated for inline classes #973

@mkrussel77

Description

@mkrussel77

THIS IS A BUG TRACKER ONLY. FOR QUESTIONS PLEASE CHECK FAQ OR USE FORUM:

http://www.jacoco.org/jacoco/trunk/doc/faq.html

https://groups.google.com/forum/?fromgroups=#!forum/jacoco

Please understand that
ISSUES WITHOUT FOLLOWING INFORMATION WILL BE CLOSED WITHOUT COMMENTS!
Thank you for filling feature request!

Scenario

  • JaCoCo version: (from right bottom corner of JaCoCo report) 0.8.5.201910111838
  • Operating system: Mac OS
  • Tool integration: Maven / Ant / CLI / API (for others please report to respective project) Gradle
  • Description of your use case: (detailed description or executable reproducer, e.g. GitHub repo)

Kotlin generates several methods for inline classes similar to how it does for data classes.

  • equals()
  • hashcode()
  • toString()
  • getter for wrapped value

Would like inline classes to behave like data classes. I know inline classes are experimental so adding it at this point might cause breakage in the future.

Current Behaviour

All of these methods are reported as unused

Wanted Behaviour

The methods to not be reported as unused

Possible Workarounds

Use data classes instead of inline classes

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions