Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
deschutes
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
deschutes
4y ago
My complaint is that it is too easy to create an object with uninitialized members by accident. On account of the syntax being identical. I guess its too late to add affordances there. I suppose a definition of valid that prohibited uniniti
62.
▲
by
deschutes
4y ago
It depends on what you mean by "object". For example, pod types share syntax with classes but are not always initialized. What's better is that sanitizers don't detect this form of undefined behavior! (Clean on memory,ad
63.
▲
by
deschutes
4y ago
Clang tidy covers only the most trivial use after move scenarios. It's useful coverage but isn't and never will be complete like the rust borrow checker.
64.
▲
by
deschutes
4y ago
So, my understanding is that: 1. Unless otherwise initialized, types have a zero value in go. For pointer types that zero value is nil. 2. It's encouraged for this to be meaningful. That's opposed to say java, python, or C++ where
65.
▲
by
deschutes
4y ago
Why require types have a meaningful zero value? It's not necessary for value semantics. You can require that values be initialized and the machinery for that doesn't seem that bad. Zero values seem as arbitrary as requiring all ty
66.
▲
by
deschutes
4y ago
I'm not sure what you're driving at. The sibling clearly outlines a scenario where the collateral is lost. But it almost doesn't matter so long as you assume the clearinghouse isn't some vestigial intermediary. I can
67.
▲
by
deschutes
4y ago
It makes perfect sense for a regulation that intends to protect the retail customer's interests. I suspect Robinhood would put customer money up for collateral if they were allowed to do so.
68.
▲
by
deschutes
4y ago
Here's what I gather from that thread. The bottom line is that the retail trader stays whole in the case the trade fails to clear. If the broker was allowed to use the retail trader's money for collateral it would either not reall
69.
▲
by
deschutes
4y ago
I'm not sure deferred conversion is a bad thing in this toy instance. I agree that being able to easily tradeoff between time and space is an important property of compile time evaluation and C++ doesn't make that easy with the no
70.
▲
by
deschutes
4y ago
I missed that. You're right.
71.
▲
by
deschutes
4y ago
String literals are specified to have static storage duration. That means references are valid at least until main returns. In practice string literals are immortal and references to them are always valid.
72.
▲
by
deschutes
4y ago
Have to defer conversion to std string to runtime https://godbolt.org/z/rWKEr4P6h
73.
▲
by
deschutes
4y ago
In that case, the soap is the least of your problems.
74.
▲
by
deschutes
4y ago
Find me a reasonable person offended by this terminology and I'll show you an unreasonable person. That connotation doesn't come through at all.
75.
▲
by
deschutes
4y ago
I had a similar belief that ended much the same.
76.
▲
by
deschutes
4y ago
Wait till you see the rest of javascript...
77.
▲
by
deschutes
5y ago
It's amazing that a dog smelling odors could be evidence of anything, even taken in the context of other evidence. In my view the dog is simply a tool to find evidence. The tool indicating there is evidence is not evidence.
78.
▲
by
deschutes
5y ago
The problem with trans fats seems to be a matter of degree rather than kind. See the note on palm oil on Wikipedia. Also note that deaths attributable to coronary artery disease, the quantifiable thing linked to trans fat consumption, are h
79.
▲
by
deschutes
5y ago
Ok. Show me something that would be a food but for "delayed bad things". Like, delayed by decades or even years. Just so we're clear, nutritional deficiencies aren't of any interest. As far as I'm aware this angle i
80.
▲
by
deschutes
5y ago
I find reviews work best when you place a strong bias towards shipping workable if imperfect code. Quick reviews are also a strongly positive thing. On the other end are fixed processes. Have as little of this as possible, automate it if yo
81.
▲
by
deschutes
5y ago
It doesn't do a very good job of delineating the coast. Seems like +- 50 ft is black. Puget sound is unrecognizable on my display.
82.
▲
by
deschutes
5y ago
What you're describing is WhatsApp. So we don't need to speculate. iMessage benefited tremendously from being the default. Combine that with Apple's mobile market share in the US and you get the present situation. My gripe is
83.
▲
by
deschutes
5y ago
This is a hard problem and definitely not unique to Java. For example networks, or perhaps more appropriately, network protocols, have these kinds of cliffs as the offered load on the network increases. As I understand a particularly bad t
84.
▲
by
deschutes
5y ago
How can the runtime conclude that the rejection is unhandled when there are outstanding references to the Promise? In other words, as long as the promise might later be awaited or otherwise handled I don't see why the runtime should ca
85.
▲
by
deschutes
5y ago
It's pretty easy to understand. The idea is that the recommended doses are demonstrably not lethal. They may or may not be effective. The effective dose (if any) may or may not be lethal. I don't know enough to evaluate any of the
86.
▲
by
deschutes
5y ago
Memory safety bugs can be intimidating and sometimes challenging. Mostly they're not though. Conscientious programmers aren't going to spend too long in the shooting themselves in the foot phase. To me the awful compilation model
87.
▲
by
deschutes
5y ago
Model fallible instantiation with factory methods. e.g. Node::make(Args..) -> Result<Node>. It won't always be as efficient or ergonomic but it works. And hey it's c++, you've been conditioned to accept a ton of cere
88.
▲
by
deschutes
5y ago
I don't like ion. The added features (over json) don't pull their weight. Symbols, annotations and the binary format all add significant complexity but don't make the format much better. As a consequence of the added complexi
89.
▲
by
deschutes
5y ago
My opinion is based on my experience integrating artifact generators (both code and config) into a build. I recall being funneled into building a plugin by documentation to deal with some idiosyncrasies of the generator. Whereas I just want
90.
▲
by
deschutes
5y ago
Gradle does suck though.
More ›