Guillaume Lessard comments

Results 152 comments of


                                            Guillaume Lessard

strerror is not (guaranteed) to be thread safe

We might want to use `strerror_s` from C11 instead, for portability.

Conditionally enable bounds checking for unsafe buffer pointers

Nice!

Conditionally enable bounds checking for unsafe buffer pointers

> What do you think about providing specific implementations of these for UnsafeRawBufferPointer? I think the reason we hadn't done so thus far is that we got away with it....

[stdlib] Optional: Allow non-escapable wrapped types

@swift-ci please build toolchain

[stdlib] Optional: Allow non-escapable wrapped types

@swift-ci smoke test

Disfavor String.init(platformString: UnsafePointer<CChar>)

@swift-ci please test

[Bug] `superDecoder(forKey:)` doesn’t work as documented

Agreed! The important thing is to match the behaviour from macOS 13 and earlier. (rdar://118337978, for reference.)

Retarget pending changes to 1.4.0

@swift-ci please test

[gardening] Merge the release/1.3.0 branch back into main

@swift-ci please test

[gardening] Merge the release/1.3.0 branch back into main

We could update/fast-forward main to this commit if we're happy with this PR, instead of having yet another merge.