Skip to content

Use explicit method name to avoid confusion and declares better the scope - #1110

Merged
masesdevelopers merged 1 commit into
masterfrom
1100-jvmbridgebasenew-cannot-be-used-as-is-use-another-name
Jun 5, 2026
Merged

masesdevelopers merged 1 commit into
masterfrom
1100-jvmbridgebasenew-cannot-be-used-as-is-use-another-name

Conversation

@masesdevelopers

Copy link
Copy Markdown
Contributor

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@masesdevelopers masesdevelopers self-assigned this Jun 5, 2026
@masesdevelopers masesdevelopers added enhancement New feature or request JNetReflector JNetReflector related issue labels Jun 5, 2026
@masesdevelopers masesdevelopers linked an issue Jun 5, 2026 that may be closed by this pull request
@masesdevelopers
masesdevelopers merged commit 0ea9239 into master Jun 5, 2026
11 checks passed
@masesdevelopers
masesdevelopers deleted the 1100-jvmbridgebasenew-cannot-be-used-as-is-use-another-name branch June 5, 2026 03:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request JNetReflector JNetReflector related issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JVMBridgeBase.New cannot be used as is

1 participant