Port call sites from VSJ 3 #13
Draft
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 objective is to get unary and binary call sites working for representative special methods.
A lot has changed in
SpecialMethodand the type system since VSJ3. We have a clearer notion of shared representation and mutable type. This affects the detail of call sites, although the VSJ 3 design stands up well.At present, all special methods are implemented by handles that look up a descriptor on the type, which is never going to be fast. Type object initialisation and update does not need to update handles cached on the
Representationbecause they are generic. We have not so far felt it worth updating call site targets to generic handles, so none of the architecture we intend is yet in play.In order to exercise this properly, we need to generate code with call sites. A separate sub-project seems appropriate (but not as messy as
dy3bm). We shall maybe dip a toe into the code generation end of compilation.Plenty to do.