Skip to content
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

Remove the insta-stable cfg(wasm) #83981

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

nagisa
Copy link
Member

@nagisa nagisa commented Apr 7, 2021

The addition of cfg(wasm) was an oversight on my end that turns out to have a number
of downsides:

  • It was introduced as an insta-stable addition, forgoing the usual
    staging mechanism we use for potentially far-reaching changes;
  • It is a breaking change for people who are using --cfg wasm either
    directly or via cargo for other purposes;
  • It is not entirely clear if a bare wasm cfg is a right option or
    whether wasm family of targets are special enough to warrant
    special-casing these targets specifically.

As for the last point, there appears to be a fair amount of support for
reducing the boilerplate in specifying architectures from the same
family, while ignoring their pointer width. The suggested way forward
would be to propose such a change as a separate RFC as it is potentially
a quite contentious addition.

cc #83879 @devsnek

@rust-highfive
Copy link
Collaborator

r? @Mark-Simulacrum

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 7, 2021
@devsnek
Copy link
Contributor

devsnek commented Apr 7, 2021

I thought we were going to add a feature instead of removing this

@Mark-Simulacrum
Copy link
Member

I haven't checked in terms of this actually reverting the change, but in terms of the specific code patch here seems OK; r=me.

I think we should remove this support for now, and then potentially re-add with a feature gate -- it looks like the code is minimal, and I'd rather not accidentally leave it in to hit stable :)

@rust-log-analyzer

This comment has been minimized.

@nagisa
Copy link
Member Author

nagisa commented Apr 7, 2021

I thought we were going to add a feature instead of removing this

That was what I thought as well, before I realized that adding cfg(wasm) is a breaking change. cfg(wasm) being a breaking change significantly reduces the chances of it being stabilized in the future as it is, which is why I opted for a removal rather than for implementing a feature gate.

I do encourage you to continue the discussion and propose to add something like this as a separate changeset. Sorry about that.

The addition of `cfg(wasm)` was an oversight on my end that has a number
of downsides:

* It was introduced as an insta-stable addition, forgoing the usual
  staging mechanism we use for potentially far-reaching changes;
* It is a breaking change for people who are using `--cfg wasm` either
  directly or via cargo for other purposes;
* It is not entirely clear if a bare `wasm` cfg is a right option or
  whether `wasm` family of targets are special enough to warrant
  special-casing these targets specifically.

As for the last point, there appears to be a fair amount of support for
reducing the boilerplate in specifying architectures from the same
family, while ignoring their pointer width. The suggested way forward
would be to propose such a change as a separate RFC as it is potentially
a quite contentious addition.
@Mark-Simulacrum
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Apr 7, 2021

📌 Commit 54dc7ce has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 7, 2021
@bors
Copy link
Contributor

bors commented Apr 8, 2021

⌛ Testing commit 54dc7ce with merge 69e1d22...

@bors
Copy link
Contributor

bors commented Apr 8, 2021

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 69e1d22 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Apr 8, 2021
@bors bors merged commit 69e1d22 into rust-lang:master Apr 8, 2021
@rustbot rustbot added this to the 1.53.0 milestone Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants