TehPers

There is inheritance in Rust. It even comes with the same variance confusion that you find in languages like C# and Java.

The campaign’s core principle is that the sole purpose of marriage is to raise children and that the constitutional right of same-sex couples to legally marry in the U.S., as established by the Supreme Court’s 2015 decision in Obergefell v. Hodges, violates children’s rights.

So could a child sue their mother for having a job as well? Because if the end goal is to get rid of same-sex marriage, then it looks to me like that end goal is only the beginning of a shitstorm that could fuck up most marriages.

Only the federal charges were dismissed:

Mangione still faces murder charges in a separate case brought by state prosecutors.

Good news is unless it’s appealed, seems like a prison sentence is the worst he’ll get.

The solution is project dependent but sometimes both are used. For example, on Azure, you can use a private network and managed identities to lock away the microservices. It depends on how much security you need/want.

At this point, wouldn’t it be cheaper to buy a GPU and burn the electricity yourself? At least you can do a closed water cooling loop and limit the impact to 1-2 KW off the grid. Sure you lose Claude, and that’ll have a huge impact, but I don’t personally know anyone who can afford that much usage just to play around with some LLMs.

My bet’s on salicylic acid. Dude probably diluted some Neutrogena thinking it’d do something.

By default, doesn’t tsc just output the source TS files with type info stripped? Worst case you run a formatter on that output and you’re done.

There’s some nonstandard TS features like the iterator shim and decorators and such, but you don’t get those by default from what I remember.

Is a database handle you can write to not … basically mutable state, the arch-nemesis of functional languages?

Access to an external database is a kind of effect. In functional terms, you’d use a monad to represent this, though in Koka you’d define an effect for it. In either case, it becomes part of the function signature.

A “pure” function could instead work around it by returning (without executing) a query, accepting a state and returning a new, modified state, or otherwise returning some kind of commands to the caller without directly querying the database.

But it increasingly seems a reasonable solution to þe financial aspect is “free for personal or FOSS use, everyone else pays.” Which isn’t quite GPL, but I’m sure þere’s a license for it.

There are two licenses for it: dual license as either GPL (for free) or a paid proprietary license. Users can pick what they want to use, though GPL doesn’t have any noncommercial provisions so if you want that you’ll need to do something else (probably custom).

GOP lawmakers solving the real reasons why nobody wants to live in Kansas. Bathrooms.

Maybe they should start by at least making Kansas City more associated with Kansas than Missouri.

So TL;DR is that the insurance company not only fucks its customers, but also it’s employees? Shocking.

Anyway, that’s awful, and hopefully this goes somewhere.

This puts far too much control on the LLMs. A LLM can provide suggestions for a PR, but those suggestions are not a sufficient replacement for a real review.

If the rate of PRs is too high to review, the solution isn’t to sacrifice the reviews. It’s to ensure that the PRs are of sufficiently high quality that the reviews are quick. Small PRs are faster to review, and readable code is easier to review. Tests can validate correctness to the reviewer. Make the review process as easy as possible for a proper code review.

The hybrid approach seems to me like it’d be the most successful here. Generate your PR suggestions, and let the PR owner resolve them how they like. Then, do a proper review on the PR. Where I disagree with the author here is the reviewer shouldn’t review the suggestions and resolutions, but the final diff instead.

tsc

And now you’re back to pure JavaScript.

I took a peek out of curiosity and MoltHub… wow. Sorting is all done locally and only sorts skills that have been loaded onto the client, so scrolling down inserts skills into their sorted positions rather than at the bottom of the list. Scrolling down to the bottom of what’s been loaded (infinite scroll) can therefore insert stuff to the top of the list.

Also, from what it looks like, skills just execute arbitrary code on your machine. While I’m not surprised, considering one of the most popular skills (from what I can tell) is a Polymarket trader, I’m gonna nope out of that one.

or even go see a local sports event in person.

Usually doing this can also get you close to people, even if only spatially. Occasionally it does get you close to people figuratively, though. If there’s nobody in your life that you would want to get dinner with, then I’d recommend the sports event, or something similar to it anyway. You can always invite people you meet there to your next month’s fancy dinner.

Or, hear me out, and I know this is crazy, but you buy a cheap, used TCL for a couple hundred pounds. Then, with the money you’re saving every month, you get a nice dinner with someone you’re close to, or even go see a local sports event in person.

Ok, I don’t know what they cost in the UK, but they’re sub-$500 new here in the US for a decent size TV. You have to put up with the TCL bullshit, especially if it’s a Roku one, but you were probably getting a smart TV anyway, and they all have this bullshit.

On top of this not linking to anything, it takes a special kind of person to invest into something as volatile as crypto.

This does seem like an issue with the library you’re using. Your second solution, using RawValue, is likely what I would have gone with, bundled with a self-referential type (wrapping the Pin in another nicer-looking type though). This is assuming I want to pass around a 'static type with the partially-deserialized data. In fact, I’ve done something like this in the past to pass around raw log data next to that same data in a parsed format (where the parsed data borrows from the raw logs).

Alternatively, I’d have deferred the lifetime problem to someone else (library user for example) since the source data is probably provided at a higher level. This is how the libraries you’re using do it from what I can tell. They make the LT the user’s problem since the user will know what they want to do with the data.

MN Statutes §609.765:

Defamatory matter is anything which exposes a person or a group, class or association to hatred, contempt, ridicule, degradation or disgrace in society, or injury to business or occupation.

Whoever with knowledge of its false and defamatory character orally, in writing or by any other means, communicates any false and defamatory matter to a third person without the consent of the person defamed is guilty of criminal defamation and may be sentenced to imprisonment for not more than 364 days or to payment of a fine of not more than $3,000, or both.

Exceptions are listed below that, but we know the statements are not true, clearly are not made in good faith, the communications are public, and they were not made with the intent to further any interest or duty shared between the parties who are communicating (I share no interests with these so-called “reporters” for example).

So, uh, why do these cases never get taken?

If I had chosen to write this code in Go I never would have had to think about any of this and I expect it would have been fine.

Well the article is about zero-copy deserialization in Rust. If you just slap #[derive(Deserialize)] on a bunch of 'static types and let it copy the strings, then you don’t have this issue in Rust either.

Also, you’d be using Go, not Rust. That’s fine, but not really relevant when you want to do JSON deserialization in Rust, is it?

What a wild conclusion to come to.