-
Notifications
You must be signed in to change notification settings - Fork 67
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
Refer core namespace to user namespace only when building slow version #351
Merged
candid82
merged 1 commit into
candid82:master
from
jcburley:refer-core-to-user-only-when-slow
Feb 17, 2020
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
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
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.
Won't this fail compilation with
fast_init
tag sinceReferCoreToUser
is not available withfast_init
?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.
gen_code.go
(which generates thefast_init
stuff, so that doesn't actually work yet onmaster
anyway) generates an emptyReferCoreToUser
implementation intoa_code.go
. So this does work on thegen-code
branch.That's arguably a bit of a kludge, in that it could go into a proper
*.go
file compiled only with+build fast_init
.But right now there's not really any such "source" file in the ordinary sense, so I threw it into the generated
a_code.go
file.Do you want it somewhere else? E.g. a
core/fast_init.go
file, with the "slow" version going intocore/slow_init.go
? They'd start out with just this one receiver in them, but might grow over time to include more stuff that isn't really specific to other existing files.Or, we could put it in
core/environment_fast_init.go
and renamecore/environment_init.go
tocore/environment_slow_init.go
(and maybe the othercore/*_init.go
files accordingly, for consistency).(As an aside, one of the things I absolutely adore about Go is the ability to do such simple renaming without having to edit Makefiles....)
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.
Upon further consideration, I find I'm really liking the idea of all
*_init.go
files being either*_slow_init.go
or*_fast_init.go
.I've updated my pending
gen-code
branch to put the empty implementation of this new receiver intocore/environment_fast_init.go
.Then, unless I hear otherwise from you, I'll go forward with a (separate) renaming PR, that also adds the new source file from the
gen-code
branch.But this current PR should be fine as-is, in the sense that it won't break anything.
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.
This makes sense, thanks!