Xiaodi Wu
Xiaodi Wu
This API is Swift's spelling of the IEEE scaleB operation, which is specified for both binary and decimal floating-point types, so the new behavior _is_ the correct one. Of note,...
> I don't think anyone is saying that the change isn't needed or shouldn't have been implemented. My read is that some of the comments are saying exactly that. But...
Yeah, after noodling with alternatives, I concluded that those gcd use cases that need to deal with overflow can go through the trouble of converting the _arguments_ and doing a...
My two cents here (as with gcd) would be that a "reporting overflow" version would be more consistent with how the stdlib reports overflow and (if desired) a double-width version...
> Weren't the stdlib patterns created before error handling was added to the language though? No, long after.
Posting unsolicited checkmarks to PRs that you are not authoring, for which you are not code owner or a requested reviewer, is going to be regarded as nuisance behavior in...
Re endianness, there is also the option (with pros and cons) of copying the approach used in the standard library integer types: There, an `Int` simultaneously represents both an integer...
The second sentence should be stricken entirely. The model is, instead, for any type declaration _and_ for any extension not declared with an access modifier, the implied access modifier for...
> The introduction of the label will have no effect on existing code This is not strictly true because of Swift's tuple shuffle behavior, although it is unlikely to break...
@swift-ci please test