From b8fd9080c2f95873caa79dbc7f4df6e686bbb4d9 Mon Sep 17 00:00:00 2001 From: Marcono1234 Date: Mon, 10 Jun 2024 00:24:45 +0200 Subject: [PATCH] Update JEP 471 information in README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b86bf15..51db170 100644 --- a/README.md +++ b/README.md @@ -8,9 +8,9 @@ The issue with `Unsafe` is that it does not detect out-of-bounds reads and write validation. Therefore invalid arguments can break the correctness of an application or even represent a security vulnerability. -Note that the memory access methods of `Unsafe` will probably be deprecated and removed in future JDK versions, see -[JEP draft JDK-8323072](https://openjdk.org/jeps/8323072). Libraries targeting newer Java versions should -prefer [`java.lang.foreign.MemorySegment`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/foreign/MemorySegment.html), +Note that the memory access methods of `Unsafe` have been deprecated for JDK 23 and will be removed in a future JDK +version, see [JEP 471](https://openjdk.org/jeps/471). Libraries targeting newer Java versions should prefer +[`java.lang.foreign.MemorySegment`](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/foreign/MemorySegment.html), which is a safer alternative to `Unsafe`. ### Why this sanitizer?