[1]: https://github.com/microsoft/winget-pkgs/tree/master/manifes...
2,236 karma · joined April 3, 2024
[1]: https://github.com/microsoft/winget-pkgs/tree/master/manifes...
However, not all C constructs have idomatic Rust equivalents. For example, bitfields don't exist in Rust, and unlike Rust enums, C enums can have any value of the underlying type. And for ABI reasons, it's very commom in C APIs to use a pointer to an opaque type paired with what are effectively accessor function and methods, so mapping them to accessors and methods on a "Handle" type in Rust often is the most idomatic Rust representation of the C interface.
1. It symlinks redundant bin and lib directories to /usr/bin, and its packages don't install anything to /usr/local.
2. You can keep most config files in /etc or $XDG_CONFIG_HOME. Occasionally software doesn't follow the standards, but that's hardly the distro's fault.
3. Arch is bleeding edge
4. Arch repos are pretty big, plus thete's the AUR, plus packaging software yourself from source or binaries is practically trivial.
5. Security is not the highest priority over usability. You can configure SELinux and the like, but they're not on by default. See https://wiki.archlinux.org/title/Security.
6. There are few defaults to adhear to on Arch. Users are expected to customize.
> We were recently notified that certain games on Steam may violate the rules and standards set forth by our payment processors and their related card networks and banks
Individual games violating "rules and standards" doesn't really fit with prohibiting a category because of high rates of fraud.
Vim's inconsistent keybinds and behavior are what pushed me to Kakoune — which I find has more consistent and elegant bindings and behavior — in the first place, and Helix feels like a step backwards on that front.
Yes, exactly; the linear regions are needed to more evenly distribute precision, while the average precision remains the same. Alternatively, you can omit the mantissa, but use an exponent base much closer to 1 (perhaps 1 + 2⁻²³).
I wouldn't call using a uninhabited type for the type of a return expression theoretically inelegant. On the contrary, I find it quite pleasing.
Basically, I expect users wil stil need a way to defend against permission spam.
Why should Bethesda have to refine the same exact formula over and over? That would just turn into what Ubisoft does with Assassins Creed, pumping out soulless entry after entry into the franchise. In other words, Starfield was Bethesda taking a risk and trying to introduce unique features rather than releasing yet another another predictable "Bethesda RPG".
I'm not a lawyer, so my question is genuine.
Maybe it's a case of [1], but I think Plasma is ready for the average desktop user. The other parts of the system may have some ways to go.
2. Sort factors in ascending order
3. Set var diagram to a single dot
4. Foreach factor in factors
4.1. Set var diagram to factor copies of diagram aranged in a circle
And that's not just said out of unfamiliarity. I'm a professional C++ developer, and I often find I'm more familiar with C++'s more arcane semantics than many of my professional C++ developer co-workers.
> for_each(a.begin(), a.end(), std::cout << _1 << ' ');
Also, Scala has something similar as a first class feature[2].
[1]: https://www.boost.org/doc/libs/1_88_0/doc/html/lambda.html
[2]: https://scala-lang.org/files/archive/spec/3.4/06-expressions...