Go Package Initialization
Situation:
A Go package A is composed of 3 .go
files, and I use functions from another package B in each of these files. I have to import package B at the beginning of each file.
Question:
Is package B actually initialized 3 times or only 1 time?
go
add a comment |
Situation:
A Go package A is composed of 3 .go
files, and I use functions from another package B in each of these files. I have to import package B at the beginning of each file.
Question:
Is package B actually initialized 3 times or only 1 time?
go
add a comment |
Situation:
A Go package A is composed of 3 .go
files, and I use functions from another package B in each of these files. I have to import package B at the beginning of each file.
Question:
Is package B actually initialized 3 times or only 1 time?
go
Situation:
A Go package A is composed of 3 .go
files, and I use functions from another package B in each of these files. I have to import package B at the beginning of each file.
Question:
Is package B actually initialized 3 times or only 1 time?
go
go
edited Nov 15 '18 at 0:30
Rene Knop
1,3633722
1,3633722
asked Jul 18 '13 at 20:25
Seth Archer BrownSeth Archer Brown
6633823
6633823
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Short answer: Initialization will be performed only once.
Long answer: Quoting the relevant specification section - Program execution:
A package with no imports is initialized by assigning initial values to all its package-level variables and then calling any package-level function with the name and signature of
func init()
defined in its source. A package-scope or file-scope identifier with name
init
may only be declared to be a function with this signature. Multiple such functions may be defined, even within a single source file; they execute in unspecified order.
Within a package, package-level variables are initialized, and constant values are determined, according to order of reference: if the initializer of A depends on B, A will be set after B. Dependency analysis does not depend on the actual values of the items being initialized, only on their appearance in the source. A depends on B if the value of A contains a mention of B, contains a value whose initializer mentions B, or mentions a function that mentions B, recursively. It is an error if such dependencies form a cycle. If two items are not interdependent, they will be initialized in the order they appear in the source, possibly in multiple files, as presented to the compiler. Since the dependency analysis is done per package, it can produce unspecified results if A's initializer calls a function defined in another package that refers to B.
An
init
function cannot be referred to from anywhere in a program. In particular,init
cannot be called explicitly, nor can a pointer toinit
be assigned to a function variable.
If a package has imports, the imported packages are initialized before initializing the package itself. If multiple packages import a package P, P will be initialized only once.
The importing of packages, by construction, guarantees that there can be no cyclic dependencies in initialization.
A complete program is created by linking a single, unimported package called the main package with all the packages it imports, transitively. The main package must have package name
main
and declare a functionmain
that takes no arguments and returns no value.
func main() { … }
Program execution begins by initializing the main package and then invoking the function
main
. When the functionmain
returns, the program exits. It does not wait for other (non-main) goroutines to complete.
Package initialization—variable initialization and the invocation of
init
functions—happens in a single goroutine, sequentially, one package at a time. Aninit
function may launch other goroutines, which can run concurrently with the initialization code. However, initialization always sequences theinit
functions: it will not start the nextinit
until the previous one has returned.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17733220%2fgo-package-initialization%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Short answer: Initialization will be performed only once.
Long answer: Quoting the relevant specification section - Program execution:
A package with no imports is initialized by assigning initial values to all its package-level variables and then calling any package-level function with the name and signature of
func init()
defined in its source. A package-scope or file-scope identifier with name
init
may only be declared to be a function with this signature. Multiple such functions may be defined, even within a single source file; they execute in unspecified order.
Within a package, package-level variables are initialized, and constant values are determined, according to order of reference: if the initializer of A depends on B, A will be set after B. Dependency analysis does not depend on the actual values of the items being initialized, only on their appearance in the source. A depends on B if the value of A contains a mention of B, contains a value whose initializer mentions B, or mentions a function that mentions B, recursively. It is an error if such dependencies form a cycle. If two items are not interdependent, they will be initialized in the order they appear in the source, possibly in multiple files, as presented to the compiler. Since the dependency analysis is done per package, it can produce unspecified results if A's initializer calls a function defined in another package that refers to B.
An
init
function cannot be referred to from anywhere in a program. In particular,init
cannot be called explicitly, nor can a pointer toinit
be assigned to a function variable.
If a package has imports, the imported packages are initialized before initializing the package itself. If multiple packages import a package P, P will be initialized only once.
The importing of packages, by construction, guarantees that there can be no cyclic dependencies in initialization.
A complete program is created by linking a single, unimported package called the main package with all the packages it imports, transitively. The main package must have package name
main
and declare a functionmain
that takes no arguments and returns no value.
func main() { … }
Program execution begins by initializing the main package and then invoking the function
main
. When the functionmain
returns, the program exits. It does not wait for other (non-main) goroutines to complete.
Package initialization—variable initialization and the invocation of
init
functions—happens in a single goroutine, sequentially, one package at a time. Aninit
function may launch other goroutines, which can run concurrently with the initialization code. However, initialization always sequences theinit
functions: it will not start the nextinit
until the previous one has returned.
add a comment |
Short answer: Initialization will be performed only once.
Long answer: Quoting the relevant specification section - Program execution:
A package with no imports is initialized by assigning initial values to all its package-level variables and then calling any package-level function with the name and signature of
func init()
defined in its source. A package-scope or file-scope identifier with name
init
may only be declared to be a function with this signature. Multiple such functions may be defined, even within a single source file; they execute in unspecified order.
Within a package, package-level variables are initialized, and constant values are determined, according to order of reference: if the initializer of A depends on B, A will be set after B. Dependency analysis does not depend on the actual values of the items being initialized, only on their appearance in the source. A depends on B if the value of A contains a mention of B, contains a value whose initializer mentions B, or mentions a function that mentions B, recursively. It is an error if such dependencies form a cycle. If two items are not interdependent, they will be initialized in the order they appear in the source, possibly in multiple files, as presented to the compiler. Since the dependency analysis is done per package, it can produce unspecified results if A's initializer calls a function defined in another package that refers to B.
An
init
function cannot be referred to from anywhere in a program. In particular,init
cannot be called explicitly, nor can a pointer toinit
be assigned to a function variable.
If a package has imports, the imported packages are initialized before initializing the package itself. If multiple packages import a package P, P will be initialized only once.
The importing of packages, by construction, guarantees that there can be no cyclic dependencies in initialization.
A complete program is created by linking a single, unimported package called the main package with all the packages it imports, transitively. The main package must have package name
main
and declare a functionmain
that takes no arguments and returns no value.
func main() { … }
Program execution begins by initializing the main package and then invoking the function
main
. When the functionmain
returns, the program exits. It does not wait for other (non-main) goroutines to complete.
Package initialization—variable initialization and the invocation of
init
functions—happens in a single goroutine, sequentially, one package at a time. Aninit
function may launch other goroutines, which can run concurrently with the initialization code. However, initialization always sequences theinit
functions: it will not start the nextinit
until the previous one has returned.
add a comment |
Short answer: Initialization will be performed only once.
Long answer: Quoting the relevant specification section - Program execution:
A package with no imports is initialized by assigning initial values to all its package-level variables and then calling any package-level function with the name and signature of
func init()
defined in its source. A package-scope or file-scope identifier with name
init
may only be declared to be a function with this signature. Multiple such functions may be defined, even within a single source file; they execute in unspecified order.
Within a package, package-level variables are initialized, and constant values are determined, according to order of reference: if the initializer of A depends on B, A will be set after B. Dependency analysis does not depend on the actual values of the items being initialized, only on their appearance in the source. A depends on B if the value of A contains a mention of B, contains a value whose initializer mentions B, or mentions a function that mentions B, recursively. It is an error if such dependencies form a cycle. If two items are not interdependent, they will be initialized in the order they appear in the source, possibly in multiple files, as presented to the compiler. Since the dependency analysis is done per package, it can produce unspecified results if A's initializer calls a function defined in another package that refers to B.
An
init
function cannot be referred to from anywhere in a program. In particular,init
cannot be called explicitly, nor can a pointer toinit
be assigned to a function variable.
If a package has imports, the imported packages are initialized before initializing the package itself. If multiple packages import a package P, P will be initialized only once.
The importing of packages, by construction, guarantees that there can be no cyclic dependencies in initialization.
A complete program is created by linking a single, unimported package called the main package with all the packages it imports, transitively. The main package must have package name
main
and declare a functionmain
that takes no arguments and returns no value.
func main() { … }
Program execution begins by initializing the main package and then invoking the function
main
. When the functionmain
returns, the program exits. It does not wait for other (non-main) goroutines to complete.
Package initialization—variable initialization and the invocation of
init
functions—happens in a single goroutine, sequentially, one package at a time. Aninit
function may launch other goroutines, which can run concurrently with the initialization code. However, initialization always sequences theinit
functions: it will not start the nextinit
until the previous one has returned.
Short answer: Initialization will be performed only once.
Long answer: Quoting the relevant specification section - Program execution:
A package with no imports is initialized by assigning initial values to all its package-level variables and then calling any package-level function with the name and signature of
func init()
defined in its source. A package-scope or file-scope identifier with name
init
may only be declared to be a function with this signature. Multiple such functions may be defined, even within a single source file; they execute in unspecified order.
Within a package, package-level variables are initialized, and constant values are determined, according to order of reference: if the initializer of A depends on B, A will be set after B. Dependency analysis does not depend on the actual values of the items being initialized, only on their appearance in the source. A depends on B if the value of A contains a mention of B, contains a value whose initializer mentions B, or mentions a function that mentions B, recursively. It is an error if such dependencies form a cycle. If two items are not interdependent, they will be initialized in the order they appear in the source, possibly in multiple files, as presented to the compiler. Since the dependency analysis is done per package, it can produce unspecified results if A's initializer calls a function defined in another package that refers to B.
An
init
function cannot be referred to from anywhere in a program. In particular,init
cannot be called explicitly, nor can a pointer toinit
be assigned to a function variable.
If a package has imports, the imported packages are initialized before initializing the package itself. If multiple packages import a package P, P will be initialized only once.
The importing of packages, by construction, guarantees that there can be no cyclic dependencies in initialization.
A complete program is created by linking a single, unimported package called the main package with all the packages it imports, transitively. The main package must have package name
main
and declare a functionmain
that takes no arguments and returns no value.
func main() { … }
Program execution begins by initializing the main package and then invoking the function
main
. When the functionmain
returns, the program exits. It does not wait for other (non-main) goroutines to complete.
Package initialization—variable initialization and the invocation of
init
functions—happens in a single goroutine, sequentially, one package at a time. Aninit
function may launch other goroutines, which can run concurrently with the initialization code. However, initialization always sequences theinit
functions: it will not start the nextinit
until the previous one has returned.
edited Aug 26 '15 at 19:37
Flimzy
38.8k106597
38.8k106597
answered Jul 18 '13 at 20:36
zzzzzzzz
54.2k12130114
54.2k12130114
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17733220%2fgo-package-initialization%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown