TehPers

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.

Do you want to? Go for it.

Does your game crawl? Have you identified this code as the bottleneck? Are you certain that asm will give you a meaningful performance increase, and that your issue doesn’t lie with your approach to the problem? Sure, I guess. You said your game runs fine though, so this probably doesn’t apply.

Is your game fast already? If you don’t want to do it, don’t.

Writing asm by hand is almost always a waste of time. There are only a few times where it’s actually necessary, and unless you’re writing a bootloader and running your game on bare metal, I can’t imagine why it’d be necessary. But you know your code better than anyone else here, so you should know whether it’s needed or not more than any of us do.

To begin with, you’re apparently targeting the Z80, which I haven’t seen used for games in the wild… probably in my entire life? Maybe an arcade machine I played on once used it, but I can’t think of any other times. If your targets need custom assembly, then you should already know that. We don’t know your targets.

I don’t disagree that running random scripts off the internet is a bad idea, and I even made that clear. I was just pointing out that these specific scripts are verifiable entirely by the URL (which is just the raw GH file URL for the file in that repo).

I agree that signing the scripts would be a good idea though. I’m not sure how hard (or expensive) it is to do so though. If it’s anything like TLS certs, it’s probably just not worth it to them (though LE exists for TLS).

You shouldn’t trust random scripts off the internet of course, but…

You do realize these scripts all come from this GitHub repo, right? It’s possible to verify them all, unless I’m missing a script here I guess. Even the registry files are plain text and readable directly in GH.

Not a lawyer, but if this isn’t a clear case of duress, then nothing is. Nobody with a functioning brain would say that someone begging a service to stop publishing generated sexual imagery of them is doing so under anything other than duress. That claim would be equivalent to saying someone agreed to your TOS when they begged you to stop stabbing their mother on your service.

to be specific, when you refer to “that all” happening, you mean Biden signing the bill that banned TikTok in April 2024, I think?

Yes. Biden happened to be president, but any president would have signed that into law because of the support, and even if it hadn’t become law, we’d still be in this position. Trump wants to control the media. He’ll do it however he needs to.

your timeline is jumping around a bit here, because now you’re referring to “that period” and linking to a source from January 2025, the time of Trump’s inauguration.

The period in question went on for quite a while (a yearish if I remember correctly). Anyway, your comment doesn’t actually say anything to contradict my point of ByteDance spreading their cheeks for Trump.

this ban only passed because Democrats were bamboozled into supporting a proposal that has its roots in Republican “omg China scary” bullshit. I don’t know how to explain it any more clearly.

You don’t need to. The ban is irrelevant. Without the ban, we’d be in the same place, with Trump attacking all forms of media to gain control.

ahh yes, “criticizing Democrats is the same thing as supporting Republicans”, the free square on the bingo board.

You’re not criticizing lawmakers here. You’re criticizing the common person, the people actually affected by the purchase. What you’re doing is essentially victim blaming.

Your entire analogy is irrelevant. The people you’re criticizing are the people who reviewed the exterminator, not the exterminator.

The ban had bipartisan support, and even if that all never happened, you’d still be in the same situation. They would have sold off their US business anyway whether they were forced to or just got a big offer.

Keep in mind that TikTok also put out messages during that period practically deep throating Trump and sent it out to all their users. This was going to happen either way.

Ironically, a ban could have prevented this from happening entirely by making TikTok no longer relevant to the US. Not that banning it wouldn’t come with other issues as well, of course.

Maybe rather than blaming those in search of a solution, you could try blaming those who created the problem. Friendly fire doesn’t do a whole lot of good, but does support Trump, which I’m assuming isn’t your goal here.

Breaking down what async fn in trait does, it converts it to a fn method() -> impl Future<Output=T>, which breaks further down into fn method() -> Self::__MethodRet where the generated associated type implements Future.

This doesn’t work for dyn Trait because of the associated type (and the fact method() needs a dyn-safe self parameter).

Instead, your methods need to return dyn Future in some capacity since that return type doesn’t rely on associated types. That’s where async_trait comes in. Box<dyn Future<...>> is a dyn-safe boxed future, then it’s pinned because async usually generates a self-referential type, and you need to pin it anyway to .poll() the resulting future.

Edit: also, being pedantic, associated types are fine in dyn traits, but you need to specify the type for it (like dyn Blah<Foo=i32>. Even if you could name the return type from an async fn, it’d be different for every impl block, so that’s not realistic here.

I was told to watch this movie with no context. It is a combination of my two least favorite movie genres. I hate that I agree with the votes.

All that happened is a shift from local officer violence to federal officer violence. The latter isn’t recorded as a violent “crime” of course.

More likely though, the pandemic’s economic effects impacted everyone. Unrest was at an all-time high. It’s not really a surprise there was a lot of crime. We’re still waiting for the bubble to pop, but wait until that happens, then compare numbers.

I suspected there was something. Last time I saw ID verification in the EU mentioned here, I think someone mentioned this there as well. Thanks for the link!

Yeah, seems to just show an image on Beehaw. Thanks!

This depends on how the verification is done, in my opinion, as well as whether there is a presence of more anonymous alternatives.

If the EU has a system which does not rely on third parties for verification and allows the platform to verify directly with a government-run service, then the only real issue there is lack of anonymity, which isn’t necessarily a bad thing on a platform if there are also popular anonymous alternatives people can use when they want to.

The article doesn’t go into how ID verification will work though. If it’s through third parties like how the US does it, then that’s disgusting and waiting to be breached.

Anyone have a link to the article? These posts don’t link properly on Lemmy.

Also, how old does it predict you are if you ask it if there’s a seahorse emoji?

You asked me a question wholly irrelevant to my comment to bait out some kind of answer you can challenge rather than actually responding. Did you expect me to answer your question?

You appear to be allergic to healthy discussion. I’m out.

Are you responding to the right person? Because if you intended to reply with that, then clearly your reading comprehension skills match your critical thinking skills.

Belief in ’race’ is racism. Prove me wrong…

Well your claim is inherently flawed. “Race” isn’t something a person believes in, it’s an observation of what is essentially human tribalism throughout history. Even if it were a thing to believe in, racism itself isn’t the belief in race, but the belief that different races (or tribes) of people are inherently worse than others in some ways.

In other words, your statement is similar to the statement “Belief in ‘sex’ is sexism”, which is hilariously wrong, and of course is predicated on the idea that people “believe” in these things.

While I agree with your post, I do want to call out that Rust’s standard library does use a lot of unstable features and calls compiler intrinsics. Anyone can use the unstable features I believe with just #![feature(...)], but not the intrinsics (not that there’s much reason to call the intrinsics directly anyway).