refactor: remove some chalkConfig field accesses #237
Merged
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.
Issue
#214
Description
Continue from #235 and #236, removing every remaining access of a
ChalkConfig
field that consists only of built-in types.With this PR, the remaining field accesses of
chalkConfig
are the below:Just to illustrate the progress: with this PR,
nimble build
succeeds if we manually replacec4autoconf.nim
with these ~430 lines (which is ~15% of the length of the autogenerated one):Click to expand
Testing
Hopefully the existing tests are sufficient.