haberman

134 ms·

1351.
by haberman 11y ago
> That's the point of continuations, though. That's a feature, not a bug. If that's what you're after, then by all means implement that. :) But I think most people would expect the Lua interpreter state to be self-co
1352.
by haberman 11y ago
The Lua implementation is a C library. You invoke it by calling C functions like lua_call(). Imagine you have a C program like this: #include <fancylib.h> int main() { for (int i = 0; i < 10; i++) { printf
1353.
by haberman 11y ago
I've never come across anything that was so effective at being depressing that I felt weighed down just from skimming it.
1354.
by haberman 11y ago
> Say you want to resume continuation K, which has a stack of some size N. The size of the continuation's stack doesn't matter for the problem I described, it's the size of the stack "underneath" your continuatio
1355.
by haberman 11y ago
> if your stack looks like Lua -> C -> Lua, then it won't work. I don't think you can safely solve this in the general case. There is a key problem I don't think you can work around. Say your stack looks like C(1) -
1356.
by haberman 11y ago
Think of short variable names as pronouns. Like saying "it", except you have maybe 1-4 distinct "it"s. Short variable names work well for things that have common and obvious meanings. "i" for an iterator or
1357.
by haberman 11y ago
Google lets you prune already-solved parts of the search space. I have a deep understanding of the technologies I work with, but that doesn't mean I remember the three lines of code that you use to slurp a file into an STL string, for
1358.
by haberman 11y ago
I worked there from 2004-2007. I'm glad I don't really remember how many RSUs I sold at $40.
1359.
by haberman 11y ago
Yes I think this guy goes too far. But to take a more moderate stance, I think it's really interesting that while we can perceive EM waves and sound, we can do so only within limited frequency bands. The reality we perceive is a subse
1360.
by haberman 11y ago
Shoot, I have been working on an article describing the C11/C++11 memory model for many months, but it looks like he's going to beat me to it! Oh well, there can be 2 (or 3, or 4... :)
1361.
by haberman 11y ago
I've never seen government decision-making work first-hand, so I wouldn't claim that this speculation should carry weight. But if I was someone on the FBI side who wanted to "win" this somehow, I could imagine how this m
1362.
by haberman 11y ago
But the MIR definition of "safety" must be more encompassing than LLVM IR, right? LLVM IR has no concept of a borrow. Where in the MIR pipeline does borrow checking happen?
1363.
by haberman 11y ago
I'm curious how this new architecture preserves safety invariants. The post says MIR contains operations not available in Rust because they are unsafe. Does this mean every MIR transformation needs to be safety-preserving? Or is saf
1364.
by haberman 11y ago
I don't know much about this (it's not my area of expertise), but I thought this G+ post was interesting: https://plus.google.com/u/0/+VincentVanhoucke/posts/6RQmgqcm... It says that a lot of t
1365.
GPUCC – An Open-Source GPGPU Compiler(research.google.com)
195 points by haberman 11y ago|53 comments
1366.
by haberman 11y ago
I see, thanks for clarifying. I agree there could be reason to consider a change in that case.
1367.
by haberman 11y ago
I can't see an argument here for why the standard should be changed. memcpy() does one thing and memmove() does another. Changing the standard so they are the same just because memcpy() gets misused in real-world programs doesn't
1368.
by haberman 11y ago
Is there a difference between re-seeding and re-keying? I think of this analogy: you re-key/re-seed periodically not because the originally lock gets weaker, but in case someone stole your key without you knowing. Accurate?
1369.
by haberman 11y ago
Hi Chandler, I should have clarified that the comments I was referring to were on this bug: https://llvm.org/bugs/show_bug.cgi?id=11763 I was surprised to see: "I don't think it's really worth warning ab
1370.
by haberman 11y ago
Interesting! I have met some amazingly awesome people in London who I would totally hang out with if I lived there. But they are musicians, not doctors/lawyers/engineers. When I think about it more, most of my good friends come
1371.
by haberman 11y ago
FWIW, my life isn't like this at all. I'm 34 and my friends and I are all professionals. It was gorgeous in Seattle this week. Monday night I went to a BBQ with 7 of my closest friends. We spent hours on the rooftop deck of their
1372.
by haberman 11y ago
Given how aggressively compilers (including Clang) are exploiting undefined behavior these days, it is surprising to see Clang developers (I presume) on the bug being so blasé about introducing undefined behavior themselves.
1373.
by haberman 11y ago
> This is true for static and dynamic typing as well: they exist in degrees. Rust can verify type proofs that other languages can't regarding memory safety. Some languages can verify that integer indexes into an array won't go
1374.
by haberman 11y ago
> I think they do have a well-accepted definition [...] [You] shouldn't confuse your dislike for them for the absence of a well-accepted definition that's widely used in computer science literature. Just upthread, you said: &gt
1375.
by haberman 11y ago
I can't speak to the Danish and Canadian media, but the American media also glorify Barack Obama, Malala Yousafzai, Amit Singhal, Russell Wilson, Chris Rock, the Dalai Lama, Beyoncé, Bruno Mars, Prince, etc. Also the only major motion
1376.
by haberman 11y ago
The fact that "strong typing" has no universal definition is exactly why I think it's not useful.
1377.
by haberman 11y ago
> You can't misuse any kind of Ion value that is a string as if it were a timestamp without performing an explicit conversion. The same is true of JSON. There is no difference, except that Ion has a timestamp type and JSON does not
1378.
by haberman 11y ago
By your definition, any language with strings is weakly typed, since you can always interpret a string as being something else. Strongly/weakly typed has never been a particularly useful description (as the page you linked notes), and
1379.
by haberman 11y ago
That is a good point in that it is a very accurate reading of the JSON spec. In practice many (even most) JSON implementations don't give applications access to any precision beyond what an IEEE double can represent. So while you may
1380.
by haberman 11y ago
Sure, I think your "poorly typed" vs. "richly typed" axis just refers to how many built-in types it has. It's true that CSV and INI only have one type (string). And it's true that when more types are built in

More ›