-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: remove remaining chalkConfig field accesses (#329)
Continue (from past commits [1][2][3]) to prepare for the new con4m, by reducing our usage of the autogenerated types and procs. This time, remove nearly every remaining access of a chalkConfig field. The two remaining field accesses are in the `get` overloads: $ git grep --break --heading --ignore-case --context=1 'chalkConfig\.' src/run_management.nim 30:proc get*[T](chalkConfig: ChalkConfig, fqn: string): T = 31: get[T](chalkConfig.`@@attrscope@@`, fqn) 32: 33:proc getOpt*[T](chalkConfig: ChalkConfig, fqn: string): Option[T] = 34: getOpt[T](chalkConfig.`@@attrscope@@`, fqn) We'll remove those later. Refs: #214 [1] 66a5bb4, "refactor: begin to avoid autogenerated getters" [2] 4157b58, "refactor: reduce usage of autogenerated getters, part 2" [3] 855197e, "refactor(confload, subscan): remove chalkConfig field accesses"
- Loading branch information
Showing
18 changed files
with
223 additions
and
162 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.