Strongly-typed MMTk options #5
Merged
Conversation
This file contains hidden or 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
After the MMTKBuilder refactoring in mmtk-core, mmtk-ruby now has access to the strongly-typed Options struct. This allows us to provide a strongly-typed API for setting the options, instead of serializing option values into strings and set them via environment variables or API functions based on string-parsing. We now provide API for setting the plan and the heap size. More options can be made available later. Environment variables MMTK_* still work.
wks
force-pushed
the
strongly-typed-options
branch
from
569997c to
989740f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After the MMTKBuilder refactoring in mmtk-core, mmtk-ruby now has access
to the strongly-typed Options struct. This allows us to provide a
strongly-typed API for setting the options, instead of serializing
option values into strings and set them via environment variables or API
functions based on string-parsing.
We now provide API for setting the plan and the heap size. More options
can be made available later. Environment variables MMTK_* still work.