-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add no-caml-startup
feature flag that avoids the caml_startup
symbol
#37
Merged
Merged
Changes from all commits
Commits
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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
// Copyright (c) Viable Systems and TezEdge Contributors | ||
// SPDX-License-Identifier: MIT | ||
|
||
const OCAML_INTEROP_NO_CAML_STARTUP: &str = "OCAML_INTEROP_NO_CAML_STARTUP"; | ||
|
||
fn main() { | ||
println!( | ||
"cargo:rerun-if-env-changed={}", | ||
OCAML_INTEROP_NO_CAML_STARTUP | ||
); | ||
if std::env::var(OCAML_INTEROP_NO_CAML_STARTUP).is_ok() { | ||
println!("cargo:rustc-cfg=feature=\"no-caml-startup\""); | ||
} | ||
} |
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.
Shouldn't this function always call
caml_startup
? As written, callinginit
above, allowing its result to be dropped (callingcaml_shutdown
) and then callinginit
again will return anOCamlRuntime
not backed by an available runtime.caml_startup
will already avoid re-initialising if it is already running (and bumps a counter, to allow a correspondingcaml_shutdown
to behave non-destructively), so I believe it should be safe and more correct to simply delete this.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.
It should never be called from an OCaml program that wants to use Rust code, hence the panic. You only do this initialization once in your program, from your
main
function or somewhere close to it (you may for example have a separate thread that has exclusive access to the OCaml runtime, in that case you would do it there). But no function exposed to OCaml should be doing this.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.
Remember that this is nothing else more a workaround for the
dune utop
issue, the panic is in there just as a safeguard (to help anyone misusing the library), but this shouldn't be called in such case.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 don't think this is enforced anywhere: you could write
and the second call won't get an OCaml runtime. I suppose this can be a separate issue.
Edit: opened #39 for this.