您什么时候遇到现场停顿问题? [英] When have you come upon the halting problem in the field?

问题描述

您何时亲自遇到 停止问题 在该领域?可能是因为同事/老板提出了一种解决方案，该解决方案违反了计算的基本限制，或者是您意识到自己要解决的问题实际上是无法解决的.

When have you ever personally come upon the halting problem in the field? This can be when a co-worker / boss suggested a solution which would violate the fundamental limits of computation, or when you realized yourself that a problem you were trying to solve was, in fact, impossible to solve.

我最近想到的是在研究类型检查器时.我们的班级意识到，不可能编写出完美的类型检查器(该检查器将接受所有将运行且没有类型错误的程序，并拒绝所有将出现类型错误的程序)，因为这实际上可以解决暂停问题.另一个是当我们意识到在同一个类中，在类型检查阶段无法确定是否会被零除，因为在运行时检查数字是否为零也是停止问题的版本.

The most recent time I came up with it was when studying type checkers. Our class realized that it would be impossible to write a perfect type checker (one that would accept all programs that would run without type errors, and reject all programs that would run with type errors) because this would, in fact, solve the halting problem. Another was when we realized, in the same class, that it would be impossible to determine whether a division would ever occur by zero, in the type-checking stage, because checking whether a number, at run-time, is zero, is also a version of the halting problem.

推荐答案

我字面上被分配了暂停问题，如编写监视插件以确定主机是否永久关闭"中所述.严重地?好的，所以我给它一个阈值. 不，因为它可能稍后会重新出现."

I literally got assigned the halting problem, as in "write a monitor plugin to determine whether a host is permanently down". Seriously? OK, so I'll just give it a threshold. "No, because it might come back up afterward."

随之而来的是许多理论阐述.

Much theoretical exposition ensued.

这篇关于您什么时候遇到现场停顿问题?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！