fspl/arf
fspl/arf
Archived
1
1
Fork 0
Code Issues 7 Pull Requests Packages Projects Releases Wiki Activity

Update 'Guidelines'

Sasha Koshka 2022-09-29 05:26:06 +00:00
parent 6305fa6e08
commit e27a0bfe6e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Guidelines.md

@ -18,7 +18,7 @@ When solving a problem, or implementing a necessary abstraction, prefer a static
# 4. Data is Immutable by Default
Data must be immutable by default. If the user wants to modify a value at some point, they must explicitly delclare the variable to be mutable.
# 5. Manual Memory Management
We can't have anything like a garbage collector, because that violates guideline 0 and 9. A borrow checker similar to rust's could be implemented, though.
We can't have anything like a garbage collector, because that violates guidelines 0 and 9. A borrow checker similar to rust's could be implemented, though.
# 6. Zero Ambiguity
When looking at any part of ARF syntax, it should be abundantly clear what it means. A good rule of thumb is if its hard for the parser to reason about it, its hard for the user to reason about it too. Syntax should be thematically cohesive, but asymmetrical. Conceptually different things should *look* different.