mirror of
https://github.com/rust-lang/rust.git
synced 2025-04-30 20:17:50 +00:00
ed43cbcb88
remove support for the (unstable) #[start] attribute As explained by `@Noratrieb:` `#[start]` should be deleted. It's nothing but an accidentally leaked implementation detail that's a not very useful mix between "portable" entrypoint logic and bad abstraction. I think the way the stable user-facing entrypoint should work (and works today on stable) is pretty simple: - `std`-using cross-platform programs should use `fn main()`. the compiler, together with `std`, will then ensure that code ends up at `main` (by having a platform-specific entrypoint that gets directed through `lang_start` in `std` to `main` - but that's just an implementation detail) - `no_std` platform-specific programs should use `#![no_main]` and define their own platform-specific entrypoint symbol with `#[no_mangle]`, like `main`, `_start`, `WinMain` or `my_embedded_platform_wants_to_start_here`. most of them only support a single platform anyways, and need cfg for the different platform's ways of passing arguments or other things *anyways* `#[start]` is in a super weird position of being neither of those two. It tries to pretend that it's cross-platform, but its signature is a total lie. Those arguments are just stubbed out to zero on ~~Windows~~ wasm, for example. It also only handles the platform-specific entrypoints for a few platforms that are supported by `std`, like Windows or Unix-likes. `my_embedded_platform_wants_to_start_here` can't use it, and neither could a libc-less Linux program. So we have an attribute that only works in some cases anyways, that has a signature that's a total lie (and a signature that, as I might want to add, has changed recently, and that I definitely would not be comfortable giving *any* stability guarantees on), and where there's a pretty easy way to get things working without it in the first place. Note that this feature has **not** been RFCed in the first place. *This comment was posted [in May](https://github.com/rust-lang/rust/issues/29633#issuecomment-2088596042) and so far nobody spoke up in that issue with a usecase that would require keeping the attribute.* Closes https://github.com/rust-lang/rust/issues/29633 try-job: x86_64-gnu-nopt try-job: x86_64-msvc-1 try-job: x86_64-msvc-2 try-job: test-various |
||
|---|---|---|
| .. | ||
| auxiliary | ||
| use-mod | ||
| import_trait_associated_functions-2015.rs | ||
| import_trait_associated_functions.rs | ||
| issue-18986.rs | ||
| issue-18986.stderr | ||
| issue-60976-extern-use-primitive-type.rs | ||
| unused-trait-with-method-err.rs | ||
| unused-trait-with-method-err.stderr | ||
| use-after-move-based-on-type.rs | ||
| use-after-move-based-on-type.stderr | ||
| use-after-move-implicity-coerced-object.rs | ||
| use-after-move-implicity-coerced-object.stderr | ||
| use-after-move-self-based-on-type.rs | ||
| use-after-move-self-based-on-type.stderr | ||
| use-after-move-self.rs | ||
| use-after-move-self.stderr | ||
| use-associated-const.rs | ||
| use-associated-const.stderr | ||
| use-crate-self.rs | ||
| use-crate-self.stderr | ||
| use-from-trait-xc.rs | ||
| use-from-trait-xc.stderr | ||
| use-from-trait.rs | ||
| use-from-trait.stderr | ||
| use-keyword.rs | ||
| use-keyword.stderr | ||
| use-meta-mismatch.rs | ||
| use-meta-mismatch.stderr | ||
| use-nested-groups-error.rs | ||
| use-nested-groups-error.stderr | ||
| use-nested-groups-unused-imports.rs | ||
| use-nested-groups-unused-imports.stderr | ||
| use-paths-as-items.rs | ||
| use-paths-as-items.stderr | ||
| use-self-type.rs | ||
| use-self-type.stderr | ||
| use-super-global-path.rs | ||
| use-super-global-path.stderr | ||
| use.rs | ||