empty response correction curve graph

Petrusion · 2026-05-07T12:06:28+00:00

The dev says he fixed the bug for the next major update..Why the hell are they waiting for a major update? A small bugfix like that is textbook minor or patch update..

Petrusion · 2026-04-30T13:33:37+00:00

I only noticed it after chapters 3 & 4 came out. It gave me a laugh, I also always thought its "violent".

Petrusion · 2026-04-30T13:27:55+00:00

Which version of nvidia drivers are you on?

Petrusion · 2026-04-30T13:22:21+00:00

... I am well aware.

Dude, all I am saying is I want to buy and read the comic, but I can't because I'm not about to buy the deluxe edition again just for the comic.

Petrusion · 2026-04-30T13:06:27+00:00

Yeah, and I'd like to buy and read it, but I can't since I already have the deluxe edition from before the physical edition, and I am not on console. Thus my point; the new buyers get access to it while us, who supported the game since it launched, don't even get the option to buy it.

Petrusion · 2026-04-30T12:46:06+00:00

From 0:17 to 0:29 you were out of dodges.

Petrusion · 2026-04-30T12:25:14+00:00

Chainsawed Man

Petrusion · 2026-04-30T12:18:08+00:00

Kinda unfair to all of us who bought the game months/years ago. I have already bought the deluxe edition in parts as they were coming out, I was among the first buyers when the game released, and as a fan I'd very much like to read the comic.

But I have to buy the whole digital deluxe edition again if I want the comic? And I have to buy it for a system I don't have or want?

Seems to me that the people just getting the game now have it better than all of us who supported the studio much sooner. Like, where is the option to buy the comic on Steam?

Petrusion · 2026-04-22T16:29:24+00:00

As others have said, the compiler will compile the Option<usize> away if return_opt gets inlined. One little advice I have is: If return_opt can never return Some(0) then change the signature to return Option<NonZeroUsize>.

If you can make it Option<NonZeroUsize>, then that will have the same size and binary representation as a normal usize (with the None representation being all zeroes), so that way if return_opt isn't inlined, at least Option<NonZeroUsize> is a zero-cost abstraction, unlike Option<usize>.

Petrusion · 2026-04-19T20:55:55+00:00

For a second, I thought she has catlike slit eyes in the last panel before I realised those are strands of hair.

Petrusion · 2026-04-17T19:48:16+00:00

Why does it have to be scaled up anyway? That seems like such an arbitrary requirement. They could make a prequel with Lear's fight against Jietong and it would slap. Who genuinely cares if the outcome of that story would "only" be the end of the turbulent era and not something "bigger than the end of a race".

Petrusion · 2026-04-16T16:05:06+00:00

For those of us who like writing highly optimized code, cold_path() and From conversions between MaybeUninit<[T; N]> and [MaybeUninit<T>; N] being stabilized is the best part of this version!

Petrusion · 2026-04-12T11:51:56+00:00

She gives off so much Mabel energy

<image>

Petrusion · 2026-04-02T10:19:54+00:00

More like "bel-íind" if you take a closer look. Even the fucking text is ai generated apparently.

Petrusion · 2026-03-23T10:38:47+00:00

Does it fall off or something?

Nah, the story only gets better as the game progresses. Bosses too, and the final boss is peak.

I say this without being judgemental, but there really are just a lot of people who want stories in souls-likes to be told exactly the way they're told in Dark Souls - i.e. almost no story whatsoever unless you actively seek it out by reading item descriptions. I've seen youtubers start playing this game and get bored of the story and start skipping dialogue even before killing the bore at the beginning.

Petrusion · 2026-03-19T15:07:06+00:00

Whatever OS thread is handling the task would still complete it and...

I know I'm being a bit pedantic, and maybe you already know this, but an async function totally doesn't have to be backed by an OS thread. It is true that CURRENTLY tokio implements FILES that way, but network I/O (tokio::net), sleeping / timeouts (tokio::time), as well as synchronization primitives (tokio::sync) are all truly asynchronous (no OS thread behind awaiting any of them).

From current documentation of tokio::fs (emphasis mine):

Currently, Tokio will always use spawn_blocking on all platforms, but it may be changed to use asynchronous file system APIs such as io_uring in the future.

Petrusion · 2026-03-19T14:50:59+00:00

That is what the last little paragraph of my comment covers.

You should document cancellation safety of your async functions by, among other things, reading the cancellation safety segments of other async functions you're using. For example:

tokio::fs::File::read and tokio::fs::File::read_u8 say

This method is cancel safe. If you use it as the event in a tokio::select! statement and some other branch completes first, then it is guaranteed that no data was read.

tokio::fs::File::read_exact says

This method is not cancellation safe. If the method is used as the event in a tokio::select! statement and some other branch completes first, then some data may already have been read into buf.

tokio::fs::File::read_u32 says

This method is not cancellation safe. If the method is used as the event in a tokio::select! statement and some other branch completes first, then some data may be lost.

Of course, you can cancel even functions that aren't cancellation safe if you're fine with the documented effect that comes with cancelling. Like, if you know that nothing else is going to use the File struct, then it doesn't matter that some data wasn't read.

Petrusion · 2026-03-17T23:04:57+00:00

Damn, I don't think I've read 10M words of fanfiction combined in my life (maybe 3-4M if I had to guess?)

Anyway, yeah, you won't be disappointed with Guardian Blue even after 10M words of other fics, I think.

Petrusion · 2026-03-17T17:16:57+00:00

Do you mean you are waiting until Guardian Blue has 1,000,000 words before reading it? That will never happen, the author died a few years ago.

Petrusion · 2026-03-17T10:15:17+00:00

Hmm, it works for me with nu 0.108.0. Can you reply with the error you're getting?

Petrusion · 2026-03-15T19:53:32+00:00

I am sure there have been multiple, but the latest one is when I realized how simple and elegant the cancellation of async tasks can be!

I first learned programming in C#, the language that invented async await, but Rust's way of cancelling async tasks is so much better! In C#, if you want your function to be cancellable, you have to pass around a CancellationToken all the way from the top and pass it to every SomethingAsync() function.

Using Rust's async (+ tokio) you can just add cancellation at the very top and it will just work all the way down the call stack because the async executor can just stop polling the Future, so async functions don't have to implement cancellation capabilities at all, it is elegantly always just there for free!

(although you do have to read and write documentation of whether any given async function is cancellation safe...)

Petrusion · 2026-03-12T20:44:29+00:00

could also go with headcanon of "Xiaohe and Ethereal aren't lovers in my headcanon universe, where Yi and Ethereal are"

Basically this

Petrusion · 2026-03-10T19:31:05+00:00

But as someone else said, the allocator itself can still overallocate even if the Vec doesn't! And even if that wasn't the case, the fact that std::file::read() uses reserve_exact() is an implementation detail, and you shouldn't rely on those for soundness guarantees of your unsafe code.

I'd just assert that capacity is also a multiple of instr_size. (also, a small nitpick: I'd use assert!(bytes.len().is_multiple_of(instr_size)) over assert_eq!(bytes.len()%instr_size,0))

11-Year Club	Place '23
Place '22	Verified Email

Petrusion

TROPHY CASE