Repository navigation
Conversation
Accessor metadata and source syntax are independent: property, indexer and event accesses need accessor resolution, while ldftn references need method-reference resolution. Reuse the existing syntax flag and cover both paths with the isolated regression fixture. Assisted-by: OpenCode:openai/gpt-5.6-luna:OpenCode
Member
|
Hey Jeremy, thank you for the bugfix... I removed the extra "accessorSyntax" variable since |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Decompiling the class generated by this causes an error in the latest version of ILSpy, but did not in earlier versions.
Solution
The error occurs when IL references an accessor method directly—for example, using
ldftnto create a delegate to a property getter.Previously,
Disambiguator.Probe()treated every accessor method as a property or event access, even when it was being used as a method reference. That path expects an argument list, but method references leave it uninitialized, so LINQ throws ArgumentNullException.The fix distinguishes accessor syntax from accessor metadata. Actual property, indexer, and event accesses still use accessor resolution; method references use method-reference resolution instead. The regression fixture exercises a
Func<int>targeting a property getter.