Repository navigation
Support bound dot calls for LuaObject instance methods - #390
Merged
Merged
Conversation
akeit0
marked this pull request as ready for review
October 29, 2026 12:56
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.
Add
[LuaObject(BindInstanceMethods = true)]soobj.Method(...)and saved method references use the originating instance through cachedBoundClosure<T>functions.The option defaults to false, preserving explicit-receiver calls. Bound calls treat every supplied argument as a method parameter, including the bound object itself. Static methods and metamethods keep their existing conventions.
Class bindings use a lazy per-object array. Record bindings use weak-keyed arrays to preserve record equality and clone behavior.
Validation: solution build; 1,606 runtime tests on each .NET 8/10 and 73 generator tests (excluding ExpectedFailure); CSharpier. Tests cover receiver identity, inherited methods, async argument views and cancellation, ref/out, metamethods, record cloning, and argument errors.