Changed references to the C++ port to Rust.

ParaCodeLang · Oct 20, 2022 · 8f1bb16 · 8f1bb16
1 parent 9f5fe65
commit 8f1bb16
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **kwargs (Keyword Arguments)
 - More exceptions & error messages
 - Better interfacing with python code from ParaCode
-- An entire interfacing module for ParaCode/C++ communication to maintain parity and compatibility with the C++ port (Python interfacing probably won't be added to the port)
+- An entire interfacing module for ParaCode/Rust communication to maintain parity and compatibility with the Rust port (Python interfacing probably won't be added to the port)
 - A complete requests HTTP module
 - A unit tests module
 - A better icon

diff --git a/README.md b/README.md
@@ -7,7 +7,7 @@ The core library in ParaCode is written in itself, even allowing for methods to
 
 ParaCode also has many methods that have functional language characteristics for example Array mapping and lambdas, and new concept ideas such as [Prototypical Inheritance](https://en.wikipedia.org/wiki/Prototype-based_programming).
 
-I'm currently rewriting ParaCode in C++ for better speed and efficiency. I'm planning to keep ParaCode code and the standard library similar to how it is today, and even try maintaining version parity unless it becomes too much of a burden on me and the language itself.
+I'm currently rewriting ParaCode in Rust for better speed and efficiency. I'm planning to keep ParaCode code and the standard library similar to how it is today, and even try maintaining version parity unless it becomes too much of a burden on me and the language itself.
 
 [vars](https://github.com/ParaCodeLang/ParaCode/blob/rewrite/doc/00_vars.md) - How to declare and use variables