fix: Disable unused import check to prevent false positives in init function

[notJoon]

Description

There is a tendency for an unused error to occur when calling a package in the init function, even though it is actually being used. This issue appears to arise during the type-checking process performed by the go/types' Config.Check method.

Cause Analysis

It is suspected that this occurs because the types.Info structure is not provided (passed as nil) when calling Check, preventing the collection of detailed usage information.

Temporary Solution

The DisableUnusedImportCheck: true option has been added to types.Config to disable the unused import check. This serves as a temporary solution to prevent the unused error.

Future Improvements

1. Collecting detailed usage information using the types.Info structure:
   e.g.,

info := &types.Info{
    Uses: make(map[*ast.Ident]types.Object),
    Defs: make(map[*ast.Ident]types.Object),
}

2. Implementing a dedicated processing logic for tracking dependencies in the init function:
   • Special marking for packages or variables used in the init function.
   • Explicitly including init function dependencies when constructing the dependency graph.

These fundamental improvements must be addressed in the future.

Call Stack

lintTypeCheck -> TypeCheckMemPackageTest -> typeCheckMemPackage -> gnoImporter.parseCheckMemPackage -> types/config.Check

Related Issue

• False-positive unused package error #3930
• bug: gno tool lint & gno test failing when they shouldn't #3961

[Gno2D2]

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: notJoon/gno-core)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least 1 user(s) of the organization reviewed the pull request (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            └── 🔴 On no pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[jefft0]

@notJoon , please fix the failed CI checks.