From 2d448038fb6ec8ea42b366e2742b4a30088f6b95 Mon Sep 17 00:00:00 2001
From: bixb922 <70152274+bixb922@users.noreply.github.com>
Date: Sat, 4 May 2024 09:37:51 -0400
Subject: [PATCH] Added reference to the viper documentation discussion

---
 Improving-performance-with-Viper-code.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Improving-performance-with-Viper-code.md b/Improving-performance-with-Viper-code.md
index bf7d0be..f07e46a 100644
--- a/Improving-performance-with-Viper-code.md
+++ b/Improving-performance-with-Viper-code.md
@@ -744,6 +744,8 @@ Step by step with a real problem: https://luvsheth.com/p/making-micropython-comp
 
 The MicroPython tests for viper have some examples, see all cases prefixed by "viper_": https://github.com/micropython/micropython/tree/master/tests/micropython
 
+The issue that gave origin to this wiki page, with interesting discussions: [#14297](https://github.com/orgs/micropython/discussions/14297)
+
 Search https://forum.micropython.org and https://github.com/orgs/micropython/discussions for viper. There are many insights and examples.
 
 Some viper code examples here: https://github.com/bixb922/viper-examples, including a integer FFT (Fast Fourier Transform) and autocorrelation. Many examples to test or demonstrate how viper works.