forked from rebolsource/r3
-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rethink previous HIJACK commit in light of problems
Further experimenting with HIJACK revealed that direct modification of the paramlist was not a good idea, due to the potential dependencies other locations (specializations, adaptations, MAKE FRAME!s, running function calls...) might depend on the shape of that paramlist not changing. This takes back the idea of doing a replacement of the function body only if the underlying paramlists are compatible...which will be true for many adaptations, chains, or specializations from copies. It is also true for taking the function back from its original--which solves the issue of un-hijacking (one of the draws of the approach in the previous commit, but this way works). However, a non-compatible underlying function means that the frames will need to be proxied--effectively making a hijack cost similar to an extra layer of function call. At an intermediate point in trying to solve this, it was noticed that f->func is a somewhat misleading name for the frame's current function, because it changes. This changes it to f->phase and preserves the original function in f->original. Adds a non-trivial specialization test to hijack tests.
- Loading branch information
1 parent
830dd13
commit ec2d32d
Showing
25 changed files
with
206 additions
and
132 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.