Explore >> Select a destination
|
You are here 
|
usethe.computer | ||
| | | | |
tyrrrz.me
|
|
| | | | | A while ago I had to implement proper markdown parsing in DiscordChatExporter so that I could replace the brittle regular expressions I had been using. I had no idea how to approach this problem, so I spent days researching into this, eventually learning... | |
| | | | |
blog.jle.im
|
|
| | | | | Weblog of Justin Le, covering various adventures in programming and explorations in the worlds of computation physics, and knowledge. | |
| | | | |
blog.drewolson.org
|
|
| | | | | Delving into the world of pure functional programming caused me to learn about parser combinators. Upon returning to Elixir, I was excited to see that nimble_parsec is a great example of a parser combinator library for the Elixir ecosystem. Parser combinators can be notoriously confusing when first learned. In this post I'll provide a gentle introduction to parser combinators via nimble_parsec. What is a Parser Combinator? Have you ever found yourself writing a regular expression to parse input? I know I have. You finally have the syntax correct and then new requirements get added. Suddenly you need to support optional tokens, lists of values and other complicated types of input. When regular expressions start to break down because of complexity, it's time to reach for a more powerful abstraction. Enter parser combinators. | |
| | | | |
amphoragraye.com
|
|
| | | Don't query an agent that doesn't represent your genre/category. Don't query an agent that is closed to queries. Don't send it without a critique. Don't ask, "Would you like to read more?" A query letter already implies this by nature. Don't include irrelevant information (especially not in the mini synopsis). Don't talk about yourself more... | ||
