-
Notifications
You must be signed in to change notification settings - Fork 2.3k
libct/specconv: reduce init allocations, use global maps, refactor #3281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8fe1e8b
libct/specconv: rm some init allocations
kolyshkin 81586e1
libct/specconv: reuse mountPropagationMapping in parseMountOptions
kolyshkin 2c3792b
libct/specconv: make mountFlags and extensionFlags global
kolyshkin 37c5fd5
libct/specconv: make parseMountOptions return Mount
kolyshkin 6907bec
libct/specconv: remove isSecSuffix regex
kolyshkin 029b73c
libct/spec: replace isValidName regex with a function
kolyshkin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the improvement that's brought by this, but (as a follow-up) perhaps we should consider having utilities / accessor functions for these variables, so that the initialisation happens more 'organically' (reducing the cognitive overload of having to thing about first calling
initMap()whenever we need to use one of the variables.In this case it could be a function to check if
fooexists inmountPropagationMappingThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean something like
To me it looks like a bloat, since the
nsMap := getNamespaceMapping()is just a way to sugar-coatinitMaps().A runtime assertion would be nice. If only accessing a nil map would panic....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't think of anything better than
but it's still inferior to
initMaps()There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some kind of a linter to which we can add a rule (in the source code) like "X should be called before using Y" would also be nice to have.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, a lazy way to initialize variables. IOW same as this PR does, but automatically (perhaps via an annotation).
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Someone worked on something like this -- alas it does not look good without generics. https://github.com/zetamatta/go-lazy
I guess we have to postpone it till Go 2.0 ))))