3 ms·
What's your alternative when writing parsers which need to handle untrusted input? This isn't a general "use Rust everywhere" article, it's focusing on these ki
by bschwindHN 9y ago
What's your alternative when writing parsers which need to handle untrusted input? This isn't a general "use Rust everywhere" article, it's focusing on these kinds of parsers and how we can do better against very real issues.
- pjmlp 9y agoMake use of parser generators like JetBrains MPS or ANTLR. The generated parsers should take the use case of untrusted input into account. Even if they don't do it currently, it should be easier to extend a generator that will take into account while using the same grammar specification.
- andreasgonewild 9y agoBut that has nothing to do with Rust; this post and others is more or less claiming between the lines that the only thing that can save us from buggy software is the Rust way, which is bullshit. It didn't work for Java, or Erlang or Haskell; and it won't work for Rust; simply because the solution is experience, not more rules.