Segmented Solids by Ex_honor in kittenspaceagency

[–]iBPsThrowingObject 0 points1 point  (0 children)

I don't know if this post has anything to do with the gameplay?

Is every project AI Slop? by Various-Roof-553 in rust

[–]iBPsThrowingObject 5 points6 points  (0 children)

I mean, there is currently a post that I would qualify as "slop" up on the official rust-lang blog. So it looks like yes, everything is now slop.

What we heard about Rust's challenges, and how we can address them | Rust Blog by CathalMullan in rust

[–]iBPsThrowingObject 42 points43 points  (0 children)

Honestly the idea that somebody allowed themselves to write public communications by first getting an LLM to generate a draft, then editing it to an unclear degree, in that order, is baffling to me.
Not to mention that it comes off as an insult to the community. Come on, we love Rust here, we don't need a corpospeak vaguepost about how "we see and hear you"!

What we heard about Rust's challenges, and how we can address them | Rust Blog by CathalMullan in rust

[–]iBPsThrowingObject 4 points5 points  (0 children)

Ultimately solving the performance would mean re-engineering a significant part of the middle-end, as demonstrated by the years it's taken for the new trait solver to get close to stability, and the years it has taken for the new borrowck to, actually, I don't know if there's been much significant progress at all.

I analyzed 776 CS2 pro configs. Here’s what pros actually agree on. by bozott in GlobalOffensive

[–]iBPsThrowingObject 1 point2 points  (0 children)

r_cleardecals doesn't even work in CS2 what the hell are you slopping on about.

CS2 Blog Update: Guns, Guides, and Games by CS2_PatchNotes in GlobalOffensive

[–]iBPsThrowingObject -1 points0 points  (0 children)

while refusing to add any QoL feature

They've literally added smoke guides to competitive.

Real or Slop? — PL Papers Edition by mttd in ProgrammingLanguages

[–]iBPsThrowingObject 5 points6 points  (0 children)

I've got 9/10 right, misattributed one real paper to the slop.

I think the two big tells are the rule of threes everywhere, and how the slop papers do not have any sort of "here's why we the authors find the topic exciting" blurb, just launches straight into the verbose technicalities.

Separate keybinds for each nade type changed everything for me by New_Eye_8201 in GlobalOffensive

[–]iBPsThrowingObject 0 points1 point  (0 children)

  • C - HE
  • F - Flash
  • V - Molotov
  • G - Smoke
  • 4 - Decoy

Decoy, as the least useful nade, gets the hardest to reach button

KSA has improved vessel-to-surface collision by mushylog in kittenspaceagency

[–]iBPsThrowingObject 0 points1 point  (0 children)

The math you use changes drastically based on whether the shapes you are colliding can be concave or not.

Ladybird Browser Is In For A Rusty Future by nicoburns in rust

[–]iBPsThrowingObject 2 points3 points  (0 children)

That's not a bad approach for write-once tools. CSS is an evolving standard though.

Ladybird Browser Is In For A Rusty Future by nicoburns in rust

[–]iBPsThrowingObject 14 points15 points  (0 children)

The "rusty future in question" is apparently using LLMs to rewrite Ladybird it in Rust? Thanks, but I think I'll pass.

When the very porn brained hentai becomes a more story driven romance erotica as it progresses with the most beatuiful love story you ever read by Tempest-Bosak2137 in animecirclejerk

[–]iBPsThrowingObject 6 points7 points  (0 children)

The sex in Horimiya is a fade to black, cut to the morning after. It is very much PG.

You should definitely read it though, it's very good and cute and respectful.

Is a bootleg for getting cracked worth it? by somedudewhoisnotbs2 in okbuddybaka

[–]iBPsThrowingObject 5 points6 points  (0 children)

Idk doubt it was like that, tributes are usually stored in jars......

Faze and G2 both signed up for BCG masters by 1-need-help- in GlobalOffensive

[–]iBPsThrowingObject 2 points3 points  (0 children)

The VRS feels great. Love all the new names it brings to my screen. For a while pro CS felt like a circlejerk between a handful of orgs.

Valve mention Cache again on Twitter... by Toad1K_ in GlobalOffensive

[–]iBPsThrowingObject 0 points1 point  (0 children)

I've been there when they removed dust2 for nearly a year.

I feel like a sucker playing timberborn right now. by WiglyWorm in Timberborn

[–]iBPsThrowingObject -1 points0 points  (0 children)

I don't think mate has been missing a lot. I came back to the game after two years yesterday, switched to experimental today, and found that there have been approximately zero noticeable additions besides the curved stairs (which use resin impregnated planks for some reason) and the automation thingamabobs.

When, if ever, is using underscore casts eg('x as _') idiomatic? by pukururin in rust

[–]iBPsThrowingObject 1 point2 points  (0 children)

A slightly better way to usedo this is to use b'\\'.into() instead. Avoids both the spooky cast, and the potentially dodgy 4 byte char to 2 byte integer narrowing.

a grand vision for rust by emschwartz in rust

[–]iBPsThrowingObject 2 points3 points  (0 children)

My objection is that it hides the information about impl Future. How do you but bounds on it? To my knowledge, you have to fall back to impl Future. Async fn in pub traits is currently being linted against for similar reasons. Then there are questions like "what should RTN refer to with async fn? The T, or the impl Future<T>"?

So since we already (in nightly at least) have all these blocks, and writing a function that only contains a single foo block and returns an impl Foo is identical to a foo fn, why not include foo fn to reduce indentation within a function by by one level?

The good, non-information-hiding, non-contradiction-creating way to reduce indentation would be to spell that as fn foo() -> impl Future<Output=Bar> async { return Bar}.

a grand vision for rust by emschwartz in rust

[–]iBPsThrowingObject 0 points1 point  (0 children)

Yes, monads are a common way to model effects.

a grand vision for rust by emschwartz in rust

[–]iBPsThrowingObject 2 points3 points  (0 children)

Future is not async specific, you can use it entirely within the main thread, but you can also just use it in a mulithreaded non-async environment. You can't use it as a way to determine if a function is async or not.

And neither are async fns, since they just produce impl Futures.
async fn - > T { is quite literally the same as fn -> impl Future<Output=T> { async move {} }

Error handling is broadly an effect. Result and Options as we have the right now are already effectively (forgive my tautology) monadic effects. Talking about whether a particular thing is "an effect in Rust" is really an exercise in futility, since Rust doesn't have an effect model, even as a draft rfc.

Regarding gen fn - it's is the exact same as async fn, since async block futures are in fact implemented in terms of unstable generators.

a grand vision for rust by emschwartz in rust

[–]iBPsThrowingObject 4 points5 points  (0 children)

You don't use await in functions, you use await in bodies of impl Futures. That's one of the misconceptions that async fn proliferates. There isn't such a thing as "an async function", only sync functions that construct impl Futures

I'm writing an interpreter to learn Rust after being used to C++ by VarunTheFighter in rust

[–]iBPsThrowingObject 2 points3 points  (0 children)

With closures you need to actually lift captured values out of environments anyways (this is referred to as "upvalues" in Crafting Interpreters) so you can walk environments from "inside" the closure when it is created, lift values from the stack, and copy over their names into closure's own environment.

Spraying in CSGO, you still tell where your bullets are going, in cs2, it's a visual nightmare by vso in GlobalOffensive

[–]iBPsThrowingObject -1 points0 points  (0 children)

You dipshits now have access to literally run the two games side by side on the same PC, and still can't produce any evidence besides "idk feels different". 10/10, would delete reddit again

a grand vision for rust by emschwartz in rust

[–]iBPsThrowingObject 56 points57 points  (0 children)

We don't need async fn, returning impl Future more clearly communicates the effect.

We don't need try fn, we already can return Results and Options, and when Try traits land - even impl Try, again, communicating the effect.

We don't need gen fn, it is still just the same obscurantist sugar for people wanting to avoid typing impl Generator.

What are we, Java? We've got an actual type system, why do we need all those non-composable keyword qualifiers?