assert: refactor internal func getLen()

[dolmen]

Summary

Refactor internal function getLen in package assert.

Changes

• Commit1: Simplify the recover in the implementation of getLen
• Commit2: Reverse return values in the function signature to be more consistent with stdlib style (ex: os.LookupEnv)

Motivation

Cleanup, speed.

[dolmen]

@CodiumAI-Agent please review

[CodiumAI-Agent]

How to use PR-Agent

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve: Suggest improvements to the code in the PR.
/ask <QUESTION>: Pose a question about the PR.

To edit any configuration parameter from 'configuration.toml', just add -config_path=. For example: '/review --pr_reviewer.extra_instructions="focus on the file: ..."'

[dolmen]

@CodiumAI-Agent /review

[CodiumAI-Agent]

PR Analysis

• 🎯 Main theme: Refactoring of the getLen function in the assert package
• 📌 Type of PR: Refactoring
• 🧪 Relevant tests added: No
• ✨ Focused PR: Yes, the PR is focused as it clearly states in the title and description that it is a refactoring of the getLen function in the assert package. All changes in the PR are related to this refactoring.
• 🔒 Security concerns: No, the changes made in this PR do not introduce any security concerns as they are purely refactoring of existing code and do not involve any security-sensitive operations.

PR Feedback

• 💡 General PR suggestions: The refactoring seems to be well done, with the function signature being changed to align with the standard library style. The use of recover has also been simplified. However, it would be beneficial to add some tests to ensure that the refactored function behaves as expected.

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve: Suggest improvements to the code in the PR.
/ask <QUESTION>: Pose a question about the PR.

To edit any configuration parameter from 'configuration.toml', just add -config_path=. For example: '/review --pr_reviewer.extra_instructions="focus on the file: ..."'

[reza-ryte-club]

LGTM

[brackendawson]

Conventions, yes. 👍