Explore >> Select a destination
|
You are here 
|
thume.ca | ||
| | | | |
typesanitizer.com
|
|
| | | | | A discussion of different developer tools which (can) build on top of a compiler, and how those affect compiler design. | |
| | | | |
andreabergia.com
|
|
| | | | | This post is part of the Writing a JVM in Rust series. In this post, I will discuss how rjvm parses .class files. The code I will discuss today is contained in the reader crate. A warning before you read: this is the earliest part of the project and, since I have written this project to learn Rust, it is also the one that contains the least idiomatic code. Don't take this as an example of the best Rust ever written! | |
| | | | |
healeycodes.com
|
|
| | | | | Writing an interpreter from scratch. | |
| | | | |
madebyme.today
|
|
| | | Some time ago, during a code review, I had a discussion with a colleague of mine about preferring dict() over {} in new Python code. They argued that dict() is more readable - and expresses intent more clearly - therefore should be preferred. I wasn't convinced by that, but at that time I didn't have any counterarguments, so I passed. Yet that made me wonder: what's the difference between the dict type and {} literal expression? | ||
