How long until support gets added for repos with merge queues? I'd love to use this at $WORK and so would my coworkers, but we can't turn off the merge queue so we can't use stacked PRs until they can mix.
Not GP but I feel like there's a continual process of the stdlib adding some new functionality to make one such crate redundant (e.g. is-terminal in 1.70), but it isn't done yet.
I noticed my 13 thermally handles being on a soft surface (like a bed or a couch) very poorly, it gets quite warm to the touch and runs the fans hard even at rest. Does the improved thermals of the 13 pro also help this case?
Similar story here. Mine is 3 years old, and the battery is about 80% of its original capacity and the touchpad occasionally drops clicks, but otherwise it's still working great! Also the charging cable frayed, but I have plenty of those cables around.
> how, after 6 months' travel in deep space, will they accomplish anything at a Mars base, even mere survival?
I expect the answer is spin gravity. Have a long cable with a counterweight on the other end, spin it at some rate. We would need some studying about the exact impacts (how hard is it to learn to start/stop compensating for Coriolis forces?), but it'd be much easier than full weightlessness.
> I’m only claiming that it’s memory safe and I am defining what that means with high precision
Do you have your definition of memory safety anywhere? Specifically one that's precise enough that if I observe a bug in a C program compiled via Fil-C, I can tell whether this is a Fil-C bug allowing (in your definition) memory unsafety (e.g. I'm pretty sure an out-of-bounds read would be memory unsafety), or if it's considered a non-memory-safety bug that Fil-C isn't trying to prevent (e.g. I'm pretty sure a program that doesn't check for symlinks before overwriting a path is something you're not trying to protect against). I tried skimming your website for such a definition and couldn't find this definition, sorry if I missed it.
I typically see memory safety discussed in the context of Rust, which considers any torn read to be memory-unsafe UB (even for types that don't involve pointers like `[u64; 2]`, such a data race is considered memory-unsafe UB!), but it sounds like you don't agree with that definition.
I don't have sources on hand, but my understanding is that there are a lot of people who come to CA without a good plan nor a social support network, become homeless, and then people misinterpret that situation as them coming here while homeless, which then gets misinterpreted as homeless people being intentionally shipped here.
Maybe this isn't the case for you, but a number of creators I watch have some videos that they only upload to Nebula. So it's worth it for me to see those videos I otherwise wouldn't ever get to see.
There's a lint for indexing an array, but not for all maybe-panicking operations. For example, the `copy_from_slice` method on slices (https://doc.rust-lang.org/std/primitive.slice.html#method.co...) doesn't have a clippy lint for it, even though it will panic if given the wrong length.
Will it be possible to upgrade my current framework laptop to the new 16" form factor? It feels like it should be a possible upgrade, but I haven't seen anything saying that it will be possible, so I'd like to confirm.
Those things are fine, but many companies will e.g. register a separate company in a tax haven, give that company a piece of IP, and then have that company charge the original company for all of their profits. That way, the company has no profits to report, but the money wasn't reinvested in any way, just routed around profits taxes.
In my experience, LibreOffice Draw usually messes up the formatting of any PDFs I open in it. Nothing entirely unsalvageable, but text gets slightly moved around and winds up overlapping other text in a way that's annoying for future readers of the document.
If you run an advertising company, you could probably just pay people a small amount of money to get their browsing history and their FLoC id, and enough people would take you up on that offer that you'd get that data (and maybe also demographics), without having to do any work to reverse-engineer.
Many people do code against some sort of VM, but there are still people writing code in C/C++/Rust/Go/&c that gets compiled to machine code and run directly.
Also, even if you're running against a VM, your VM is running on an ISA, so performance differences between them are still relevant to your code's performance.
But is it ideal for a "Hello, world" program to follow all best-practices? In my opinion, a "Hello, world" program should do the bare minimum to print "Hello, world" to the screen, and no more, so that it represents the language at its most basic.
But what if I want to show off to my friends how smart I am by rattling off a gazillion digits of pi off of the top of my head? I need more than 10 digits to do that...
Firefox has a bookmarks sidebar that pops up if you press Ctrl+B (or buried inside the hamburger menu, but Ctrl+B is the easiest way to access it). You can put the bookmark in there, and then only open the bookmarks menu when you want to access it.
One thing that I like about Rust is that they actually allow you to merge those two into one. In your documentation of anything, you can include code snippets, and those code snippets become tests that can ensure that the documented behavior still applies to the current code.
I'm a current college student, and my school costs about $80k per year, counting tuition, room & board, supplies, etc., before financial aid. That would be $320k for 4 years, well over a quarter of a million.
I'm personally getting a significant amount of financial aid, so that it will end up costing much less than that for me, but I know people who are paying full price.
I also use it on the rare occasions where I need to log in on someone else's computer. This way, I know all my logins will be ended when I close the browser.
Theoretically, server-side analytics could use the user-agent strings and other headers in the request to have infallible analytics. In practice, a lot of server-side analytics in practice rely on third-party tracking scripts (like Google Analytics) and other such practices that get blocked by tools like Privacy Badger, etc.