Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
volta83
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
121.
▲
by
volta83
5y ago
These discussions are worth having. Avoiding the discussions and "forking the frontend to do a different thing" because "omgz rustc docs are bad and rustc devs can't be trusted" doesn't seem too valuable to me
122.
▲
by
volta83
5y ago
If you think you found a bug: you just open it. Reviewers / authors / community determine whether its a bug in the compiler or in the spec or both, or not. - How do you know that's something is a compiler bug? Compiler writer
123.
▲
by
volta83
5y ago
I think what's useful would be to have someone certify the Rust toolchain for some of these. That's what's needed to enable anyone to develop safety critical apps without issues. The problem is that most certification consult
124.
▲
by
volta83
5y ago
When was the latest Rust stable release - every 6 weeks - that did not change the "spec" at all, e.g., by adding new stable features or standard library APIs ?
125.
▲
by
volta83
5y ago
There are many levels of certification. This project is in Central Europe. A different team uses it in satellite micro controllers in the US, but I am not involved with that. I don't know of any safety certification process that requir
126.
▲
by
volta83
5y ago
> I have literally had to read compiler source code to find out Rust behavior before, more than once. That should never happen. Can you point us to the documentation bugs that you filled upstream for each of these issues ? I think it wo
127.
▲
by
volta83
5y ago
Not really. Source: I use Rust in automotive where MISRA C is required, and the only thing we needed was to certify it. No ISO standard required. We actually also supplied a "fork" of the MISRA C doc, crossing out ~80% of it, sinc
128.
▲
by
volta83
5y ago
Given that "Rust is the spec", and it changes on a daily bases, fuzzing it vs GCC Rust would give you a lot of disagreements, that would only tell you about the thousands of ways in which GCC Rust is not conforming with Rust. I&#x
129.
▲
by
volta83
5y ago
> I have literally had to read compiler source code to find out Rust behavior before, more than once. Every single time I had to do this, I opened a PR to the Rust reference with the fix. :shrug: > That should never happen. Sure, and
130.
▲
by
volta83
5y ago
> if you disagree with the unilateral decisions of the rustc developers? "Go fork it or write your own"? Yeah that's what we're doing If that's what you want to do, that's great. If you experiment with new s
131.
▲
by
volta83
5y ago
So why don't you use the GCC backend for rustc?
132.
▲
by
volta83
5y ago
rustc is backend agnostic, and currently has: an LLVM backend, a Cretonne backend, and a GCC backend. So rustc can already target _more_ architectures than this new GCC frontend, because it supports LLVM and Cretonne.
133.
▲
by
volta83
5y ago
How is rustc a single point of failure ?
134.
▲
by
volta83
5y ago
The "official" Rust frontend has a GCC backend that delivers this same value. There might be other value that a separate Rust frontend delivers over the official one, but this is not it.
135.
▲
by
volta83
5y ago
To provide a second opinion, you can just open a rustc bug. In fact, the Rust bug repository has thousands of opinions about thousands of things.
136.
▲
by
volta83
5y ago
> One reason is that having multiple implementations can be useful to ferret out issues, Do we have proof backing up this claim? For example, a list of new previously-unrepported bugs that have been uncovered by the GCC Rust re-implement
137.
▲
by
volta83
5y ago
The Rust organization maintains, amongst other things, the Rust specification (called The Rust reference). If someone wants to volunteer the 1000 expert man year required to, say in 10 years (with 100 experts), submit a probably 10 year ou
138.
▲
by
volta83
5y ago
The false positive rate reported in the blogpost for imagenet was 1 in a trillion, and the author concludes that this algorithm is better than they expected.
139.
▲
by
volta83
5y ago
That's the main reason i did it that way. I never managed a 360 hard flip on flat, but i could do them over 2 stair steps. If you are used to do hard flips very vertically, its really hard to do a 360 hardflip, even over stairs.
140.
▲
by
volta83
5y ago
The downvotes you are getting is for not reading the article. Your comment is not on-topic.
141.
▲
by
volta83
5y ago
Really interesting to see the hardflip animated vertically but the inward heelflip isn't. I always did hard flips as varial kickflips, but with fs-shuv instead of bs-shuv.
142.
▲
by
volta83
5y ago
Either the writer of the concept "opts-in to making the concept opt-in" (e.g. using the approach above), and that way, classes must opt in, _or_ classes opt-out by not implementing the concept API. There is no way for a class to b
143.
▲
by
volta83
5y ago
+1. Having worked at both, the main difference between SV and Europe is "share your failures so that everybody can learn" vs "downplay your failures so that you look better".
144.
▲
by
volta83
5y ago
Not sure what the downvotes are for, but ExaFLOP != ExaFLOP for a long time. An A100 is an ExaFLOP GPU, if you count INT8 as FLOP. Then you have the 10 different flavors of FP8, FP16, etc. and even the multiple flavors of FP32. What people
145.
▲
by
volta83
5y ago
Rust traits are opt-in, C++ concepts are opt-out; you can think of C++ concepts as having a "blanket" implementation for all types, so you'd need to opt out using negative reasoning. For example, in C++, you can declare a tra
146.
▲
by
volta83
5y ago
ExaFLOP != ExaFLOP
147.
▲
by
volta83
5y ago
Dude i don't know what you don't get it. Tesla is saying their hardware is 10x better than the competition. I don't believe it. They don't publish any numbers, and everybody else does. You believe them. Good for you. I d
148.
▲
by
volta83
5y ago
> But they've got no obligation to prove anything to random people on the internet. They are a publicly traded company. I'm a tesla investor and deserve to know. If they are right and their hardware is 10x better than the compe
149.
▲
by
volta83
5y ago
When a company claims that their new vaccine cures cancer, but is against applying for FDA approval because "no reasons given", you seem to be the kind of person that camps in front of their offices overnight to get the first 10 s
150.
▲
by
volta83
5y ago
> Not clear what you're disputing here? The article, that assumes "FLOPS on paper == FLOPS in practice".
More ›