6 Commits

Author	SHA1	Message	Date
Allan Shortlidge	491a43a66b	AST: Re-baseline MemorySafetyAttributes feature.	2025-07-31 10:21:55 -07:00
Doug Gregor	1b2fad1e78	Properly recurse when removing "unsafe" from inlinable code ... I forgot that I have to manually recurse in the syntactic rewriter. Do so. Fixes rdar://147877042	2025-03-25 16:27:37 -07:00
Doug Gregor	ae6ae33201	[SE-0458] Drop "unsafe" effect for for..in loop in inlined code in interfaces ... Only compilers can't handle it, so drop it for now.	2025-02-26 22:06:48 -08:00
Doug Gregor	983046f792	[SE-0458] Suppress @unsafe conformances for compilers that can't handle them	2025-02-26 22:06:45 -08:00
Doug Gregor	b7b5a2a19d	[SE-0458] Enable unsafe expressions / attributes / for..in effects by default ... With the acceptance of SE-0458, allow the use of unsafe expressions, the @safe and @unsafe attributes, and the `unsafe` effect on the for..in loop in all Swift code. Introduce the `-strict-memory-safety` flag detailed in the proposal to enable strict memory safety checking. This enables a new class of feature, an optional feature (that is *not* upcoming or experimental), and which can be detected via `hasFeature(StrictMemorySafety)`.	2025-02-26 12:30:07 -08:00
Doug Gregor	13c82c6f78	Remove "unsafe" keyword from expressions when printing inlinable code ... To help older compilers that don't yet support the unsafe expression deal with the Swift interface files we produce, remove the "unsafe" from expressions in inlinable code.	2025-02-18 07:14:18 -10:00