-
Notifications
You must be signed in to change notification settings - Fork 64
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
refactor(language.rust): check wasmwasi target and return error if mismatched #1382
base: main
Are you sure you want to change the base?
Conversation
5283bcd
to
97ea81b
Compare
LGTM, and I've approved the PR but we'll need either @kpfleming or @philippschulte to handle merging this PR and the subsequent new major release. |
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 looks great! I compared your changes to what Kevin recommended in the ticket. We're not cutting a new release before this has been tested and approved by Kevin. I would recommend to build binaries and share it internally for testing.
@@ -144,12 +147,17 @@ func (r *Rust) Dependencies() map[string]string { | |||
|
|||
// Build compiles the user's source code into a Wasm binary. | |||
func (r *Rust) Build() error { | |||
var wasmWasiTarget = r.config.WasmWasiTarget | |||
if wasmWasiTarget != RustWasmWasiTarget { | |||
return fmt.Errorf("your WasmWasi target in your config was %s, please change it to %s", wasmWasiTarget, RustWasmWasiTarget) |
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 helps to get it compiled but maybe it should also list the other required compute project changes. I am not sure about that just something to think about. Also do we already have a public page with instructions or is this something we decided not to do anymore?
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.
good question, the vibe i was getting is that we generally don't expect people to provide their own configs and that they'll use the default. But it's good to check that assumption, i'll poke around
…smatched Breaking change to support Rust 1.84 and newer BREAKING CHANGE: Only the wasm32-waip1 build target is accepted if a non default config is provided
b9a2a4c
to
c7c0910
Compare
30cc440
30cc440
to
c7c0910
Compare
Breaking change to support Rust 1.84 and newer
BREAKING CHANGE:
Only the wasm32-waip1 build target is accepted if a non default config is provided
All Submissions:
New Feature Submissions:
Changes to Core Features:
Are there any considerations that need to be addressed for release?
this is a breaking change and will require a major version bump to prevent breakages