From 7057af668bb478233ffb2f517fb5f5c87cc75dcb Mon Sep 17 00:00:00 2001 From: Runxi Yu Date: Thu, 5 Dec 2024 20:08:56 +0800 Subject: e^2 --- Makefile | 2 +- README.md | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 579aa92..2a4029d 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ .PHONY: upload README.html: README.md - pandoc -so README.html -c style.css README.md + pandoc --mathml -so README.html -c style.css README.md upload: README.html style.css rsync --mkpath README.html style.css runxiyu.org:/var/www/docs/e2/ diff --git a/README.md b/README.md index 8d7936d..618783e 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,10 @@ --- -title: e2 language testing space +title: $e^2$ language testing space author: Test_User and Runxi Yu --- +Note: The name "$e^2$" (or `e2` in ASCII) is subject to change. + Many languages attempt to be "memory safe" by processes such as reference counting, borrow checking, and mark-and-sweep garbage collection. These, for the most part, are guided towards preventing programmer error that causes @@ -14,7 +16,7 @@ memory safe languages) do not handle stack overflows correctly; although dynamic allocation failures could be easily handled, correctly-written programs could crash when running out of stack space, with no method to detect this condition and fail gracefully. - +) Conventional memory safety features are not our priority, but we may choose to include them in the future, likely with reference counting while allowing weak pointers to be labelled. -- cgit v1.2.3