From f5c4671bfbad96bf346bd7e9a21fc4317b4959df Mon Sep 17 00:00:00 2001
From: Indrajith K L
Date: Sat, 3 Dec 2022 17:00:20 +0530
Subject: Adds most of the tools

---
 .../v/old/vlib/crypto/internal/subtle/aliasing.v   | 29 ++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 v_windows/v/old/vlib/crypto/internal/subtle/aliasing.v

(limited to 'v_windows/v/old/vlib/crypto/internal/subtle/aliasing.v')

diff --git a/v_windows/v/old/vlib/crypto/internal/subtle/aliasing.v b/v_windows/v/old/vlib/crypto/internal/subtle/aliasing.v
new file mode 100644
index 0000000..e09748e
--- /dev/null
+++ b/v_windows/v/old/vlib/crypto/internal/subtle/aliasing.v
@@ -0,0 +1,29 @@
+// Copyright (c) 2019-2021 Alexander Medvednikov. All rights reserved.
+// Use of this source code is governed by an MIT license
+// that can be found in the LICENSE file.
+// Package subtle implements functions that are often useful in cryptographic
+// code but require careful thought to use correctly.
+module subtle
+
+// NOTE: require unsafe in future
+// any_overlap reports whether x and y share memory at any (not necessarily
+// corresponding) index. The memory beyond the slice length is ignored.
+pub fn any_overlap(x []byte, y []byte) bool {
+	// NOTE: Remember to come back to this (joe-c)
+	return x.len > 0 && y.len > 0 && // &x.data[0] <= &y.data[y.len-1] &&
+	// &y.data[0] <= &x.data[x.len-1]
+	unsafe { &x[0] <= &y[y.len - 1] && &y[0] <= &x[x.len - 1] }
+}
+
+// inexact_overlap reports whether x and y share memory at any non-corresponding
+// index. The memory beyond the slice length is ignored. Note that x and y can
+// have different lengths and still not have any inexact overlap.
+//
+// inexact_overlap can be used to implement the requirements of the crypto/cipher
+// AEAD, Block, BlockMode and Stream interfaces.
+pub fn inexact_overlap(x []byte, y []byte) bool {
+	if x.len == 0 || y.len == 0 || unsafe { &x[0] == &y[0] } {
+		return false
+	}
+	return any_overlap(x, y)
+}
-- 
cgit v1.2.3