Evaluate parens in refinement dispatch, ~10% speedup #145
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 previous semi-hack of an evaluation trick so that get-words would
evaluate in paths has been upgraded to a much less hacky trick. This
now allows for the evaluation of parens to also be used to get the words
to use as refinements in dispatch:
The method by which this is done--as well as reducing the number of
writes done into call frames--has improved performance in a build of
the hostilefork.com using the static builder by 10%. This means Ren/C
optimized non-debug builds are--for the first time--ever so slightly
faster than the rebolsource download (in that measurement).