Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let execute-component return <component-result>. #78

Merged
merged 1 commit into from Feb 5, 2016

Conversation

waywardmonkeys
Copy link
Member

This increases duplication of calling make to create the result,
but it allows for execute-component to do something different to
create results unlike the current arrangement.

This change lays the ground work for an improvement in how
benchmarks are implemented.

  • run.dylan
    (maybe-execute-component): Update to create result in skipped
    case, otherwise, use result returned from executing the component.
    (execute-component): Change return value to be a result and
    create and return the result.

This increases duplication of calling make to create the result,
but it allows for execute-component to do something different to
create results unlike the current arrangement.

This change lays the ground work for an improvement in how
benchmarks are implemented.

* run.dylan
  (maybe-execute-component): Update to create result in skipped
   case, otherwise, use result returned from executing the component.
  (execute-component): Change return value to be a result and
   create and return the result.
cgay added a commit that referenced this pull request Feb 5, 2016
Let execute-component return <component-result>.
@cgay cgay merged commit 42be597 into master Feb 5, 2016
@waywardmonkeys waywardmonkeys deleted the execute-component-values branch February 5, 2016 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants