Explore >> Select a destination
|
You are here 
|
patshaughnessy.net | ||
| | | | |
thomascountz.com
|
|
| | | | | markie | |
| | | | |
dusty.phillips.codes
|
|
| | | | | In earlier articles, I introduced this "WAT to Wasm compiler in Roc" project, wrote some Roc code to load an input file, and implemented a tokenizer for a "hello world" of Wat to Wasm compilation. It was... more work than I expected. Four blog posts more work, to be precise! I have no idea where it's going to end. But I do know what's next! Parsing. Reminder: You are reading content that took a great deal of effort to craft, compose, and debug. | |
| | | | |
bloeys.com
|
|
| | | | | In 'Thought 2: Regex is Like Assembly' I wondered why we are still doing regex in this kind of hard to understand, symbolic way, when we have already invented high level programming languages. There is no reason regex can't be written as clearly as any other programming language we use today. I thought doing this would be an interesting project, and so I came up with Regexl, a high level language for writing regex, that can be used as a simple library. | |
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
