-
Notifications
You must be signed in to change notification settings - Fork 161
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
feat(config) Add the CompilerKind
and EngineKind
types
#213
Conversation
bors try |
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.
Seems good to me, I would just have added a test for IsCompilerAvailable
but it may only introduce code duplication 🤔
Yeah, it's not that simple to test actually. I consider that if the wasmer-go/wasmer/config_test.go Lines 29 to 91 in 9ea145a
|
bors r+ |
This patch introduces the
CompilerKind
andEngineKind
types.This patch also introduces the
IsCompilerAvailable
andIsEngineAvailable
functions. They must be used to check whether a specific compiler or engine is available, otherwise theConfig.Use*Compiler
orConfig.Use*Engine
may panic.This patch also fixes a bug with the
Config.Use*Compiler
methods where thewasm_config_set_engine
function was called instead ofwasm_config_set_compiler
.