I changed the name of 2 tags : "SELECTED" into "PREFERRED" and "TO_BE_REMOVED" into "NOT_PREFERRED" because it's more specif and it explains better the context of the tags.
I added some comments to explains in details some part of the code.
I refactored the name of functions related to these tags.
I changed the name of the function "updateFactorizationNodes" to remove the ambiguity with "computeFactorizationNodes"
Motivation and Context
This refactoring is required because it's better to understand with these new names and it prevents ambiguity
How Has This Been Tested?
No test required, because it's only refactoring and the program already works.
Type of files
[ ] bin: Binary files
[ ] ci: Continuous integration files
[ ] doc: Documentation files
[x] Plain-text source code files
Level of change
[ ] break: Breaking change
[ ] exp: Experimental change
[ ] tmp: Temporal change
[ ] major: Major change
[x] minor: Minor change
[ ] sec: Vulnerability-related change
[ ] None of the above (normal change)
Type of change
[ ] deprecat: Deprecation of a once-stable feature
[ ] enhance: Enhancement in existing functionality
[ ] fix: Bug fix
[ ] feature: New feature
[ ] hotfix: Hotfix for bugs
[x] refactor: Improve coding style, comments
[ ] remove: Remove a feature
Checklist:
[x] My code compiles
[x] My code follows the code style of this project
[x] My code includes javadoc/doxygen where appropriate
[x] My code is well factored, so that there is not repetitive code in the wild
[x] My code does not require a change in the documentation, if so I already opened an issue to list the changes
[x] I have read the CONTRIBUTING document
[x] I have read the Commit Message Guidelines
[x] I understand that all commits on my pull request will be squashed to a single good one
Description
I changed the name of 2 tags : "SELECTED" into "PREFERRED" and "TO_BE_REMOVED" into "NOT_PREFERRED" because it's more specif and it explains better the context of the tags. I added some comments to explains in details some part of the code. I refactored the name of functions related to these tags. I changed the name of the function "updateFactorizationNodes" to remove the ambiguity with "computeFactorizationNodes"
Motivation and Context
This refactoring is required because it's better to understand with these new names and it prevents ambiguity
How Has This Been Tested?
No test required, because it's only refactoring and the program already works.
Type of files
bin
: Binary filesci
: Continuous integration filesdoc
: Documentation filesLevel of change
break
: Breaking changeexp
: Experimental changetmp
: Temporal changemajor
: Major changeminor
: Minor changesec
: Vulnerability-related changeType of change
deprecat
: Deprecation of a once-stable featureenhance
: Enhancement in existing functionalityfix
: Bug fixfeature
: New featurehotfix
: Hotfix for bugsrefactor
: Improve coding style, commentsremove
: Remove a featureChecklist: