HackerTrans
TopNewTrendsCommentsPastAskShowJobs

tinganho

no profile record

comments

tinganho
·2 anni fa·discuss
Note, the origins are stated in Wikipedia:

> Many papers and textbooks refer the definition and proof of undecidability of the halting problem to Turing's 1936 paper. However, this is not correct.[19][24] Turing did not use the terms "halt" or "halting" in any of his published works, including his 1936 paper.[25] A search of the academic literature from 1936 to 1958 showed that the first published material using the term “halting problem” was Rogers (1957). However, Rogers says he had a draft of Davis (1958) available to him,[19] and Martin Davis states in the introduction that "the expert will perhaps find some novelty in the arrangement and treatment of topics",[26] so the terminology must be attributed to Davis.[ https://en.wikipedia.org/wiki/Halting_problem#Origin_of_the_...
tinganho
·2 anni fa·discuss
Isn’t the channel variable declared and inferred as an int32? Can’t see why the overload isn’t resolved directly?
tinganho
·2 anni fa·discuss
One thing that crossed my mind when I was looking at the TypeScript compiler. Was that it was parsing header "d.ts" files even though it wasn't used in source. Although, it had some references of a type in a small main function.

Iirc, I think this was how most compilers did. The downside is that transitive deps can easily explode. Thus, compiling a super small main function can takes seconds.

I did suggest a solution to just lazily parse/check symbols if they are encountered in source. Instead of when including a type, you have to parse all the transitive header files of the file that defines the type.
tinganho
·2 anni fa·discuss
A thing can be explained with its constituent parts or explained by a parallel analogy. If you don't understand the constituent parts or the analogy or there are neither of these. You won't understand it.