roca

86 ms·

961.
by roca 6y ago
What hardware supports shared memory record-and-replay in the presence of data races? I'm not aware of any widely available hardware that does this. UndoDB's design is similar to rr but they use binary instrumentation at record ti
962.
by roca 6y ago
Some small-ish items: -- Virtualization of rr's required PMU features on Azure and GCP -- Virtualization of Intel's CPUID faulting on AWS and other cloud providers (Linux KVM has it, but it's not enabled in AWS) -- Fix the re
963.
by roca 6y ago
This is very cool stuff. Keno is a great rr contributor, and I'm grateful for his Pernosco shout-out :-). This sort of capability has always been part of my vision for rr/Pernosco. I want to see more projects like this doing recor
964.
by roca 6y ago
Compile-time function evaluation is quite a different feature from macros. Most of what you would do with macros (e.g. output entirely new definitions of functions, types, etc) can't be done with constexpr at all.
965.
by roca 6y ago
If you really want that, it seems better to provide them properly like Rust proc-macros than to provide them in C++'s awful half-baked form.
966.
by roca 6y ago
The problem here is that C++'s metaprogramming facilities have leaked into the parser to the extent that it's undecidable whether to parse that final declaration as a variable declaration or a function declaration. So: arguably th
967.
by roca 7y ago
In New Zealand, at least, I have no trouble conducting daily life using Web sites. I do have a smartphone but I don't use it for banking or shopping or government interactions. If my trust in Google and Apple declined I could downgrade
968.
by roca 7y ago
I care about America, but I live in NZ where the situation is much better (so far) and effective contract tracing is undoubtedly going to be very important.
969.
by roca 7y ago
> They included in the article that we could use decentralized contact tracing instead GACT is decentralized. The article is arguing against decentralized contact tracing. > a feature that is a net loss for society The article doesn&#
970.
by roca 7y ago
There's no obligation, it just means it's not a good article.
971.
by roca 7y ago
> To those who might argue that we "don't have time to delay" and need to rush this functionality out, then I would respond that a rushed solution can often be worse than doing nothing -- especially if there is no easy way
972.
by roca 7y ago
The author isn't even saying there's no viable alternative. They're just leaving it open. That is particularly troublesome since in this case, unlike your hypothetical, there is obvious value in having faster and more accurat
973.
by roca 7y ago
The article is entirely premised on Apple and Google not giving users control over whether tracing is enabled. Indeed, if they don't, that would be bad. If they do, the concerns in this article do not apply. > GACT creates a dormant
974.
by roca 7y ago
There is strong evidence against that, based on retesting flu survey samples collected in Seattle in Jan/Feb 2020. https://twitter.com/trvrb/status/1249414291297464321
975.
by roca 7y ago
There is strong evidence COVID-19 was not circulating in the Bay Area in January. Samples collected by the Seattle Flu Study in Jan/Feb 2020 have been retested and COVID-19 was not found before Feb 21. As Trevor Bedford says, had COVID
976.
by roca 7y ago
That's true but that seems to be an inevitable consequence of the Rust ownership model. Which means this is just another example of where the "one big innovation" in Rust just isn't orthogonal to other language design is
977.
by roca 7y ago
It's true that the preferred idiomatic approach to implementing error types hasn't stabilized. However, that "churn" has all been in third-party crates, so > a lot of this churn could have happened "in userspac
978.
by roca 7y ago
How would putting them in a new edition help in practice?
979.
by roca 7y ago
Low-investment hobbyist Rust projects don't need to be idiomatic. Rust hasn't broken backwards compatibility except for a few soundness fixes that broke hardly anyone. It sounds like your EmberJS experience was pretty different.
980.
by roca 7y ago
What was worse about Rust 1.0's error handling that, say, Typescript's Result? They look very similar to me. What do you mean by "a lot of churn"? The only significant thing I can think of is that the try! macro turned i
981.
by roca 7y ago
I don't think it makes sense to design a language by picking the closest existing suitable language and adding one major innovation. You want to do the minimal innovation necessary to achieve your goals --- no more, no less. Rust desig
982.
by roca 7y ago
Honestly I haven't found those things to be problems at all. ".await" really isn't confusing. I think you meant "adding 'async'" to a function declaration --- it seems fine, but I personally don'
983.
by roca 7y ago
> If you're going to change the compiler, it's pretty compelling to opt for the language that one of your team designed. It might be compelling if that person sticks around. But given Chris Lattner already moved on, it doesn&#x
984.
by roca 7y ago
I feel that the changes to date haven't been that significant. Adding `dyn` was almost completely automated, removing the need for `extern crate` was welcome and very easy to apply, likewise `try!()` to `?`. The changes to futures were
985.
by roca 7y ago
Yes, large projects like Firefox and Chrome are constantly updating their code. The rate at which that change happens varies though. Sometimes you do that because the new stuff is a significant improvement in its own right, but you also nee
986.
by roca 7y ago
I like being able to write safe and GC-free code by default. Rust would be even better if it was possible to opt into GC, but I would still want to to be GC-free by default. It's good that the entire library ecosystem has grown up GC
987.
by roca 7y ago
Able to run, yes. But it is not the default, ergonomic way to write D code like it is in C, C++ and Rust.
988.
by roca 7y ago
Ignoring "volatile" would actually break a lot of code, because it's typically used where common optimizations must not be performed.
989.
by roca 7y ago
The rational argument for what is being proposed is that companies with (total) hundreds of millions of lines of C++ code can migrate it incrementally and (hopefully) mostly mechanically as the language evolves ... which should be much chea
990.
by roca 7y ago
Linux's stable kernel ABI makes tools like rr and strace much easier to maintain. It sounds like maintaining rr for FreeBSD would be harder since you'd have to keep updating its syscall model for changes to existing syscalls as we

More ›