For debuggers it's probably the same: if they make the assumption that you need less than complete freedom in instrumenting the code, you will need print and if they don't assume that, they likely are harder to use than the language itself.
111 karma · joined February 17, 2019
For debuggers it's probably the same: if they make the assumption that you need less than complete freedom in instrumenting the code, you will need print and if they don't assume that, they likely are harder to use than the language itself.
Which safe parser generator would you recommend for writing a protobuf parser (preferably one that yields at least 25% of the throughput claimed by the OP)?
Full disclosure: I believe there is no such thing, and if what you're asking the OP is to write one, it would likely benefit greatly from generating code that leverages tail recursion. Yeehaw!
Pretty design for what it does, though!
(autocorrection got me wrong)
Usually nobody cares for unreliable code because the "correct" bit can't be figured in most cases. And people messing with the code base kind of just failed the fizzbuzz test.
First world problems, my guess.
Sleep deprivation has effects similar to alcohol consumption: impaired reasoning ability leads to mild euphoria because you forget about your conflicts and are also happily expectant to go _back to bed_ very soon.
Measure theory (for your volume) and the structure of dimensional quantities [1] are non-trivial topics, and while probably not giving good answers, I think the article is certainly asking good questions.
[1] https://terrytao.wordpress.com/2012/12/29/a-mathematical-for...
Your JS fad of the day likely ain't even considering.
> Two objects with non-overlapping lifetimes may have the same id() value.
I've always thought AT&T syntax is made for machines & debugging compiler output while Intel syntax is made for people and large scale coding...
Artificial water shortages are already a thing it seems.