Introduce a normalization chapter #2266
Open
+118
−129
Conversation
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
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.
I kind of just asborbed the new solver normalization chapter into this one because it was super out of date and seemed better to move what bits of information it had that were still current somewhere alongside all the other norm information. Though I feel like the context referring to "in new solver, in old solver" is somewhat yikes in this chapter :< to some degree it feels required since you do have to think about both solvers when deciding what normalization method to use...
🙏 new solver stabilizes and this can be cleaned up xd
I need to do some more re-reads so consider this mostly un-self-reviewed