From 7d6d1d1f607629625413d62c51b0c9f4c81cefe5 Mon Sep 17 00:00:00 2001 From: Shawn Landden Date: Sat, 1 Sep 2018 11:08:13 +0000 Subject: [PATCH] NaNs do not have signedness. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From IEEE-754 standard: Conversion of a quiet NaN in a supported format to an external character sequence shall produce a language-defined one of “nan” or a sequence that is equivalent except for case (e.g., “NaN”), with an optional preceding sign. (This standard does not interpret the sign of a NaN.) --- std/fmt/index.zig | 5 ----- 1 file changed, 5 deletions(-) diff --git a/std/fmt/index.zig b/std/fmt/index.zig index 80af750f3d..f859c6fd1d 100644 --- a/std/fmt/index.zig +++ b/std/fmt/index.zig @@ -1034,11 +1034,6 @@ test "fmt.format" { const result = try bufPrint(buf1[0..], "f64: {}\n", math.nan_f64); assert(mem.eql(u8, result, "f64: nan\n")); } - { - var buf1: [32]u8 = undefined; - const result = try bufPrint(buf1[0..], "f64: {}\n", -math.nan_f64); - assert(mem.eql(u8, result, "f64: -nan\n")); - } { var buf1: [32]u8 = undefined; const result = try bufPrint(buf1[0..], "f64: {}\n", math.inf_f64);