Explore >> Select a destination
|
You are here 
|
vlad.website | ||
| | | | |
xnacly.me
|
|
| | | | | Why i think you should write your own programming language | |
| | | | |
healeycodes.com
|
|
| | | | | Writing an interpreter from scratch. | |
| | | | |
ahmedhosssam.github.io
|
|
| | | | | The lexical analyzer (lexer) takes a stream of characters and produces a stream of names, keywords, and punctuation marks; it discards white space and comments between the tokens. Lexical tokens have types in any programming language, example: ID foo, x, n14 NUM 73, 0, 082 REAL 3.14, 10., 1e9, 0.5 COMMA , NOTEQ != LPAREN ( RPAREN ) Punctuation tokens such as IF, VOID , RETURN constructed from alphabetic characters are called reserved words and, in most languages, cannot be used as identifiers. | |
| | | | |
educatedguesswork.org
|
|
| | | [AI summary] The text discusses Rust's memory and thread safety mechanisms, emphasizing their shared principles. It highlights how Rust enforces single ownership, clear contracts, and prevents simultaneous access to shared data. Topics include references, lifetimes, thread safety, and tools like Mutex and Arc for safe concurrency. The text also touches on Rust's approach to garbage collection and its implications for memory management. | ||
