ChrisSD

21 ms·

211.
by ChrisSD 5y ago
If you use highly unstable, nightly only, Rust features then experiencing breakage is almost a certainty. That's why they're highly unstable, nightly only, features.
212.
by ChrisSD 5y ago
But in that case they're Firefox "users", not Rust users. This distinction matters because the use of Rust is just a technical detail which ultimately the user doesn't really care about. They're benchmarking Firefox
213.
by ChrisSD 5y ago
The only thing that bugged me enough to change it are the tiles on the new tab page. The new default is an absurd degree of nested padding so that the tile icons were tiny relative to the space given for each tile. If each and every tile is
214.
by ChrisSD 5y ago
For legacy reasons, any drive path that ends in a special name, such as `AUX` will be rewritten by Win32 as the NT path `\??\AUX`. This `AUX` is a special device, not a file on the filesystem. So, for example, `C:\Users\ChrisSD\AUX` will be
215.
by ChrisSD 5y ago
Indeed. And Win32 even gives you a way to bypass the legacy behaviour. You can use `\\?\` paths, which get automatically translated to `\??\` NT paths but are otherwise left untouched.
216.
by ChrisSD 5y ago
Note that UTF-8 wasn't actually standardized until Unicode 2.0 in 1996. This was at the same time as the surrogate pairs needed for UTF-16. And UTF-8 didn't find its final form until 2003, which was around the time when it really
217.
by ChrisSD 5y ago
Tbh, I don't think you're the first person to think that but the trouble with making a "safer C" is that it's not C. Or to be more precise, it looks like C but isn't C compatible. This has ended up killing most
218.
by ChrisSD 5y ago
This is why we have judges. They can look at the totality of the evidence to determine if Shell has actually complied.
219.
by ChrisSD 5y ago
Note that `from` and `try_from` are generally preferred to using `as`, where possible. This also allows casting between non-primitive types. https://doc.rust-lang.org/std/convert/trait.TryFrom.html#exa...
220.
by ChrisSD 5y ago
I think the real problem stems from the mismatch between modern processors and the processors C was originally designed for. C programmers want their code to be fast. Vanilla C no longer gives them the tools to do that on a modern processor
221.
by ChrisSD 5y ago
Interestingly, this was a mistake even the creators of UTF-8 wanted to make > The 4, 5, and 6 byte sequences are only there for political reasons. I would prefer to delete these Obviously 5 and 6 byte sequences are consigned to history b
222.
by ChrisSD 5y ago
To be technical, by "character" I mean "user-perceived character" or (in Unicode speak) "extended grapheme cluster". This is the thing a user will think of as one character when looking at it on their screen. A
223.
by ChrisSD 5y ago
Not really. Unicode is a variable width abstract encoding; a single character can be made up of multiple code points. For Unicode, 32-bit bytes would be an incredibly wasteful in memory encoding.
224.
by ChrisSD 5y ago
Validating should be pretty trivial. Explicitly handling all cases would look something like this: #[inline] const fn is_valid_scalar(c: u32) -> bool { match c { 0..=0xD7FF => true, 0xD800..=0
225.
by ChrisSD 5y ago
Turn the gcc version up to 11.
226.
by ChrisSD 5y ago
I don't think Rust has been a "Mozilla-centric" organization in a long time. Or at least the Foundation has no bearing on it. Very early on Rust was made independent of Mozilla. And since the layoffs it's hard to argue t
227.
by ChrisSD 5y ago
I think you're talking past each other. To be clear, the noscript tag "disappears" when javascript is enabled in the browser. When javascript is disabled it behaves like any other tag and can be styled accordingly. Extension
228.
by ChrisSD 5y ago
It's much simpler to develop complex libraries outside of the stdlib. And given Rust's strong stability guarantees, it can't stabilize any APIs until they're finalized anyway. So development of new APIs often happens out
229.
by ChrisSD 5y ago
Implementing crypto is much much harder than simply providing abstractions over the OS' TCP/UDP APIs. Far better to let the experts do it.
230.
by ChrisSD 5y ago
Your last paragraph is assuming they'd be interested in imposing their will upon us. They may simply not care. Meeting us may just be an interesting diversion or pure curiosity. Or they may be reluctant to get involved but sympathetic
231.
by ChrisSD 5y ago
Huh? That was exactly my point.
232.
by ChrisSD 5y ago
But that's just playing with definitions. Rephrase it as "zero runtime cost abstraction" and you get back to the intended meaning. Incidentally your first question is one that's very amenable to testing. When does the Ru
233.
by ChrisSD 5y ago
sscache has pre-built binaries on their releases page. Or you can do: cargo install --no-default-features To avoid building support for all storage backends. You can then add back any backend you're actually using.
234.
by ChrisSD 5y ago
Nothing modern about it. This is basically the C philosophy in a nutshell. Assuming "indirection" means "pointer indirection".
235.
by ChrisSD 5y ago
Sorry, I can't speak confidently on this because I can't read Japanese (or Chinese or Korean). I can only report what I've been told by users. Including language metadata with text was felt to be especially important for Japa
236.
by ChrisSD 5y ago
Given the context, I think they simply mean that a-b is interpreted the same as a - b. It can't be interpreted as a single identifier.
237.
by ChrisSD 5y ago
As far as I'm aware one problem is displaying text. Japanese readers generally need a Japanese font to correctly display Japanese text if it's Unicode. This becomes a problem when you potentially have text that can come from diffe
238.
by ChrisSD 5y ago
UTF-16 is a variable length encoding. As is UTF-32 for that matter. A single character can be made of multiple code points.
239.
by ChrisSD 5y ago
> I would want it to be implicit. Then simply use the `lossy` function. Or create an alias to it if you don't like the name.
240.
by ChrisSD 6y ago
The standalone installer is quite old and frankly weird. You're meant to use `py -3` or something like that. I don't know why it works this way. Tbh I think the official store installer works much more sensibly.

More ›