Even programming and production issues can interfere with the writing process. how good is the game's dialog parser?

甚至程和制作问题也会干扰作过程。游戏的对话解析器有多好？

So we got rid of the parser generator and we kind of like wrote it out ourselves.

于是我们摒弃了语法解析生成器，转而自解析器。

And we ended up rewriting it to use I guess what would be called like a handwritten parser.

最终，我们将其重，采了类似于手解析器的方式。

But I want Codex to do the heavy lifting for me and research how to integrate this library into my parser.

但我希望Codex能帮我完成大部分工作，研究如何将这个库集成到我的解析器中。

In fact, a lot of times I'd say, yeah, it's super easy to write a compiler if you're not writing the parser nor the code generator.

事实上，很多时候我说，是的，如果你不需要解析器和代码生成器的话， 一个译器超级简单。

One of the solutions I thought about is like, is there a way to maybe build a resume parser that does not discriminate, that doesn't rely on these discriminatory keywords and proxies?

我想过的一个解决方案是，是否有可能构建一个不带歧视性的简历解析器，它不依赖于这些具有歧视性的关键词和代理？ 我们能否构建多个不同的版本， 甚至将那些有问题的版本上传到GitHub或其他平台？