From 26564a666fe84b4bce618aade7cd63e87d9e4d03 Mon Sep 17 00:00:00 2001 From: Iain Buclaw Date: Mon, 1 Jul 2024 05:16:23 +0000 Subject: [PATCH] purge changelog --- changelog/dmd.unsafe-boolean-values.dd | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 changelog/dmd.unsafe-boolean-values.dd diff --git a/changelog/dmd.unsafe-boolean-values.dd b/changelog/dmd.unsafe-boolean-values.dd deleted file mode 100644 index f1352ae9bd..0000000000 --- a/changelog/dmd.unsafe-boolean-values.dd +++ /dev/null @@ -1,12 +0,0 @@ -`bool` values other than 0 or 1 are not `@safe` - -The spec has been updated so that only 0 and 1 are -[safe values](https://dlang.org/spec/function.html#safe-values) -for `bool`. This means that reading a `bool` value whose underlying byte representation -has other bits set is implementation-defined and should be avoided. Consequently: - -* `void` initialization of booleans is now deprecated in `@safe` code. -* Reading a `bool` field from a union is now deprecated in `@safe` code. - -Runtime array casting to `bool[]` is -[yet to be deprecated](https://issues.dlang.org/show_bug.cgi?id=24582).