SkiFire13

6 ms·

1.
by SkiFire13 4d ago
Not only that, if you have `trait Foo: Iterator<Item = u8>` and `trait Bar: Iterator<Item = i32>` how could `!` implement both of them? It would simply make the language incoherent.
2.
by SkiFire13 4d ago
Both are for for different niches, but their intersection is relatively big.
3.
by SkiFire13 5d ago
That page doesn't mention how joins between tables using different split keys work, or how indexes work.
4.
by SkiFire13 7d ago
Remember that correlation != causation. They might also have unionized due to the bad conditions while developing GTA 6, which could also lead to it being a bad game. Who knows though.
5.
by SkiFire13 7d ago
I reached the midpoint of the podcast without seeing a proper argument against this then I gave up. It tries to argue that higher reward rates are necessary to attrach customers that pay a lot (for credit card companies) and that lower inco
6.
by SkiFire13 7d ago
> credit card providers The article did an awesome job explaining what are the parties involved and you choose to use a generic term instead. > dealing with fraud and chargebacks A lot of that is offloaded to the merchant, which inste
7.
by SkiFire13 10d ago
> it’s a $14 fee per solar panel Note that usually you mount many solar panels, not just one, so this will stack relatively quickly.
8.
by SkiFire13 10d ago
The vtable contains at least the following informations: - the size of the pointed type - the alignment of the pointed type - a function pointer for its drop glue That's already quite big to inline to save on indirection, and this is b
9.
by SkiFire13 10d ago
> for some reason Just to expand on this: which vtables will be needed is not known before running codegen. At that point however multiple codegen units might generate the same vtable, and that might not get deduplicated by a later pass.
10.
by SkiFire13 10d ago
> This is possible in C++ too, but it may require extra work. Everything is possible, what matters is how much work you have to do to achieve and maintain it. > You have identical memory overhead in Rust and C++ if you store a single
11.
by SkiFire13 11d ago
No, it would mean models are good at pelicans svgs, not svgs in general.
12.
by SkiFire13 13d ago
Yes, the features don't need to be added immediately.
13.
by SkiFire13 19d ago
> I wish compilers would just have something like __builtin_memcpy and __builtin_memset The ones provided by the compilers are simply the libc ones. LLVM will even go as far as detect attempts to rewrite memcpy and replace them with a ca
14.
by SkiFire13 19d ago
The 26% slower appears to be for their whole application, not just the allocator. For some parts of the application to make the whole this much slower it must mean that those parts are quite a lot slower, likely much more than 2x. Moreover
15.
by SkiFire13 19d ago
The costs of credit cards are higher in part because of the reward programs for using such cards. That's where the wealth transfer happens, and there's nothing like this for cash.
16.
by SkiFire13 21d ago
For which key types, hashmap implementation, and hasher? Depending on these factors hashmaps performance can vary a lot.
17.
by SkiFire13 21d ago
> So O(n) could be faster than O(log n) depending on the size of the data structure and interactions with RAM pre-fetch, etc. This has always been the case. The RAM effects only changed at which point the O(n) stops being faster than the
18.
by SkiFire13 21d ago
> don't worry about low-level stuff like value/reference classes Part of the issue is that this was never low-level stuff. When you're selecting between the two you're making a semantic choice, and that's not som
19.
by SkiFire13 22d ago
It's not a good enough proxy for more people. If you compare the least and most costly items on a menu, even adjusting for size, you'll find that there's often a 2x to 4x difference between them. If I pick one over the other
20.
by SkiFire13 22d ago
> Sadly there's a rule not letting you use a known letter more than once in a word (once A is known, you can't write ALPHA) This is not entirely correct (or at least it's worded a bit weirdly). If you know that A goes in a
21.
by SkiFire13 22d ago
The thing that bugs me about tips is the fact they are a percentage. Why am I supposed to tip more if I ordered something more expensive but the service is equally good?
22.
by SkiFire13 28d ago
> flat tax FYI in some places flat taxes are technically unconstitutional
23.
by SkiFire13 29d ago
I agree with the premises, but the result proposed here doesn't look like anything I would like to use unfortunately. Even just looking at a glance you cannot see what it's doing and what each part means.
24.
by SkiFire13 1mo ago
> Whereas if you give other countries the obvious win that they can stop paying ~3% of their entire economy to a foreign payments network To be fair: - 3% is on the higher end of the fees amounts. In the EU they are now capped at 0.3% fo
25.
by SkiFire13 1mo ago
Even that way will be very difficult to make it work. The Fil-C side could change the data behind the pointer, which will not reflect on the Rust side due to the copy. Even if you manage to copy back the changes, Fil-C could also persist th
26.
by SkiFire13 1mo ago
> Kids are remarkably resilient People are remarkably resilient in general. But if chinese workers manage to survive a 996 does that make it good?
27.
by SkiFire13 1mo ago
> because they already have the code for it That's not how it generally works in most businesses.
28.
by SkiFire13 1mo ago
The word kernel always meant "the most important part of something". Likewise "harness" can be used to mean "to collect and control something so that it can be used effectively".
29.
by SkiFire13 2mo ago
As they wrote, it's "a bit sad" indeed because they cannot blame Rust for this.
30.
by SkiFire13 2mo ago
> The usual "0.1 + 0.2 != 0.3" is _not_ imprecision. It _is_ imprecision. Even if you cannot represent 0.3 exactly, you can consider the closest representable number, and that is different than the sum of the closest numbers to

More ›