Move enzymeMap to package level, compile regular expressions only once - #273
Merged
Conversation
|
|
Collaborator
|
Thanks for the PR @matiasinsaurralde! It looks like @Koeng101 defined enzymeMap as a function so that it'd behave as a constant but maybe it's no longer necessary that it does. https://qvault.io/2019/10/21/golang-constant-maps-slices/ Do you remember the reasoning behind this @Koeng101? |
Contributor
|
The reason was I just wanted an easy way to see default enzymes. However, the reasoning to put it behind a function makes sense to me. |
This file contains hidden or 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
3 participants
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 think that this might be useful and perform better if you're calling
getBaseRestrictionEnzymesmultiple times in the same function. Before this change,getBaseRestrictionEnzymeswould compile the same regular expressions over and over.