v3.0.0

[xobotyi]

As of issues with generics and unnamed initializations linter have been completely refactored - it is easier to treat it a ground-up new linter:

• Linter now uses WithStack traversal - it is simplified and improved detection of structure being initialized within return statement.
• Generics support
  fix: Generic struct is ignored #39
  close: fix: validate generics #40
• Slice and map expressions support
  fix: exhaustruct doesn't detect properties not defined in slice expressions #32
• Due to overall algorithm simplification and optimisations - raw analysis time sligntly decresed for large codebases.
• Testing improvements
• (BREAKING CHANGE!) Regular Expressions matching reworked
  Previously: type is matched even if match is partial.
  Now: type is matched only if it is a full match of full type name (including the package name).
• (BREAKING CHANGE!) Repository structure changed
  Previously: analyzer constructor exposed on /pkg/analyzer subpath.
  Now: analyzer constructor exposed on /analyzer subpath.
• (BREAKING CHANGE!) Only top level structures allowed to be unintialized during error return.
  Previously: nested structures initialization within error-containing return have been allowed to stay unintialized.

  return typ1{nested: typ2{}}, errors.New("some err")

  Now: above code will yield linting error alike pkgName.typ2 is missing field A
• (BREAKING CHANGE!) Error message has changed.
  Previously: A, B, C, D ..., Z are missing in TestType
  Now: pkgName.TestType is missing fields A, B, C, D ..., Z

[Hades32]

Now: TestType is missing fields A, B, C, D ..., Z

Could this be packagename.TestType? Would make it consistent with the new matching rules (which I'm looking forward to!)

[xobotyi]

in case you proposing that github.com/GaijinEntertainment/go-exhaustruct/v3/analyzer.analyzer becomes analyzer.analyzer - agree
otherwise, in case you proposing to output full name - it will be very hard to read the output of linter

[Hades32]

Definitely the former :)