From baeafc5ccc4a9893d22e6629db97720e3fa6d3ae Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Sun, 3 Dec 2023 09:47:38 -0600
Subject: Rename/move

---
 topics/coding-guidelines.gmi | 16 ----------------
 1 file changed, 16 deletions(-)
 delete mode 100644 topics/coding-guidelines.gmi

(limited to 'topics/coding-guidelines.gmi')

diff --git a/topics/coding-guidelines.gmi b/topics/coding-guidelines.gmi
deleted file mode 100644
index 8f83ba5..0000000
--- a/topics/coding-guidelines.gmi
+++ /dev/null
@@ -1,16 +0,0 @@
-# Coding guidelines
-
-We aim to adhere to the following coding guidelines.
-
-=> /topics/use-exceptions-to-indicate-errors Exceptions, not None return values
-=> /topics/maybe-monad Maybe monad, not None values
-=> /topics/better-logging Log messages
-=> /topics/code-antipatterns Coding Anti-Patterns
-=> /topics/lisp/debugging Debugging lisp
-=> /topics/lisp/common-lisp-sly Common LISP: sly
-=> /topics/lisp/define-condition Common Lisp Condition Handling
-=> /topics/lisp/lisp4schemers Lisp For Schemers
-=> /topics/lisp/tips-and-tricks Defining a scheme sexp comment with a reader macro
-=> /topics/profiling_python_code Profiling Python code
-
-This document is an index of other documents describing coding guidelines. Add more here as you write/discover them.
-- 
cgit v1.2.3