Draft and Discussion to figure out custom namecall self type definition #51
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.
The RFC: https://github.com/karl-police/rfcs/blob/patch-1/docs/user_defineable_self_namecall_type.md
It's basically just all about how
self
isn't controllable compared toClass.TestMethod(self: insert_type_here)
and how
:
takes away the first argument, but I am not sure if this would cause issues for the typesolver. It seems to work fine when using--!strict
when doingself = self :: ClassObject
and when looking at the Bytecode
I don't see a instruction in the code where it is processing
self = self
which makes the current alternative within pure:
functions possible, but annoying.But if Bytecode Compilation ever gets changed by Luau where
self = self
would count as a MOVE instruction, then this would be bad.