rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-04-13	UI tests: migrate remaining compile time `error-pattern`s to line annotations	Vadim Petrochenkov	-1/+0
	when possible.
2025-04-11	Rollup merge of #138904 - madsmtm:apple-test-no-std, r=tgross35	Stuart Cook	-0/+41
	Test linking and running `no_std` binaries I looked around, but it seems that we do not have a test that tests a `#![no_std]` + `#![no_main]` binary. So now I've added one. Motivated by discussion in [this Zulip thread](https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/Provide.20.60__isPlatformVersionAtLeast.60.20in.20.60std.60.3F/with/507870028). r? ```@tgross35``` try-job: arm-android try-job: armhf-gnu try-job: dist-ohos try-job: x86_64-mingw-1
2025-04-03	compiletest: Require `//~` annotations even if `error-pattern` is specified	Vadim Petrochenkov	-1/+4

2025-03-24	Test linking and running no_std binaries	Mads Marquart	-0/+41

2024-02-16	[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives	许杰友 Jieyou Xu (Joe)	-5/+5

2024-01-10	Stop mentioning internal lang items in no_std binary errors	Nilstrieb	-0/+41
	When writing a no_std binary, you'll be greeted with nonsensical errors mentioning lang items like eh_personality and start. That's pretty bad because it makes you think that you need to define them somewhere! But oh no, now you're getting the `internal_features` lint telling you that you shouldn't use them! But you need a no_std binary! What now? No problem! Writing a no_std binary is super easy. Just use panic=abort and supply your own platform specific entrypoint symbol (like `main`) and you're good to go. Would be nice if the compiler told you that, right? This makes it so that it does do that.