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.
Provides a mechanism for the GEM author to do the final processing after the blocks specified in
build.gem
have been processed.This allows GEM author and user code to be processed in the following order:
MRuby::Gem::Specification.new
inmrbgem.rake
MRuby::Build#gem
in the build configuration file.MRuby::Gem::Specification#last_initializer
inMRuby::Gem::Specification.new
.When performing library detection, I would like to use it to auto-detect when GEM users do not specify anything.
https://github.com/dearblue/mruby-stacktrace/blob/TENTATIVE.1/mrbgem.rake#L123-L144
So far, if desired to specify a block for default settings, this can be accomplished by directly assigning it to an instance variable.
However, when viewed as a public API, I do not believe this is the preferred method.
https://github.com/dearblue/mruby-stacktrace/blob/TENTATIVE.1/mrbgem.rake#L117