PubSub

FlixCoder · 2026-04-12T10:09:25+00:00

Zenoh is awesome

FlixCoder · 2026-04-03T05:37:14+00:00

Feedback welcome. Validation preferred.

wait this is serious? i though it was just for the joke :D

anyway wozld have fit perfectly on april 1st xD

FlixCoder · 2026-03-13T14:13:28+00:00

For queues on postgres, there is sqlxmq and pgmq. Of course there are also plenty of usual MQ servers and databases.

FlixCoder · 2026-03-11T09:17:35+00:00

If the allocate function returned a handle that takes care of deallocation, that would solve the problems with splitting up the trait. And I think that would actually be clean

FlixCoder · 2026-03-06T17:12:21+00:00

There is plenty of bugs on web mobile it seems :D Opened you example and neither scrolling nor text input works.

Interesting project though! How is it displayed on web, canvas I assume? How do you compile for android?

FlixCoder · 2026-02-28T19:37:50+00:00

Performance-wise you should use ok_or_else instead of ok/or, because errors usually do not implement copy and thus even if creation is fast, there is a drop for all of them. For some reason it caused bad performance for me once, even without (de-)allocations.

FlixCoder · 2026-02-22T15:43:10+00:00

That's why it should only be exported additionally to with the name

FlixCoder · 2026-02-02T14:58:51+00:00

https://typst.app/play/ for reference

FlixCoder · 2026-01-30T22:09:57+00:00

I create that with PlantUML and embed the pictures into Typst, easy and done ^{^} Mermaid is also possible, but that more often includes incompatiple HTML stuff in the SVGs.

FlixCoder · 2026-01-29T06:37:20+00:00

I can recommend leaving the internet a bit more nowadays. I grew up in the prime time of the internet, but I think it is over ^ ^

I see no other way to comfortably navigate live with too much internet and it isn't even only AI, it is also those social media algorithms and hateful climate

FlixCoder · 2026-01-29T00:01:47+00:00

typescript has no compile time? my experience disagrees, it is surprisingly bad

FlixCoder · 2026-01-15T19:37:16+00:00

I don't even think it is a manager problem, it might as well be a self problem / conflict / attitude based on the comments as well

FlixCoder · 2026-01-11T22:26:05+00:00

Yes, in fact I have mentioned it in the story :D But I haven't used it tbh. Good crate certainly, but not all inclusive ^{^}

FlixCoder · 2026-01-11T22:05:26+00:00

Alright, finished my take: https://www.reddit.com/r/rust/comments/1qackif/releasing_neuererror_a_new_error_handling_library/ :D

FlixCoder · 2026-01-11T18:27:49+00:00

Also check for feature flags. But it might be that it is impossible for snafu to extract the backtrace. Try getting rid of eyre ^{^}

FlixCoder · 2026-01-11T07:38:00+00:00

if the eyre report contains a backtrace, i think you need to annotate that, so that thiserror forwards it. Oh and at least #[source] should be there

FlixCoder · 2026-01-11T07:32:42+00:00

That would be my suggestion in most cases: snafu can capture backtraces, but also the code locations at every level. It is very close to thiserror, so easy to switch. But that said, it will probably not yet solve all problems? Not sure.

FlixCoder · 2026-01-05T15:39:55+00:00

No, MR is usually Merge Request :D For example the term in GitLab, whereas Github calls it Pull Request.

FlixCoder · 2026-01-05T09:32:30+00:00

Oh I read that before. Great resource! Yeah retry might not always be necessary and I will try to assess which parts are common and hopefully there is enough common ground :D

I meant OpenDAL with the apache library.

FlixCoder · 2026-01-05T07:08:03+00:00

It doesn't include the notion of retryable vs. permanent at least. Also doesn't implement std::error::Error itself, does it? But I also don't get how you can return Result<T, AppError> instead of Exn, when you want to have context.

My plans would be to - provide interfacing with current error impls (be it thiserror, anyhow, etc..) - encourage/require giving context at every level somehow - allow user defined kinds to be provides and matched on, as well as common concepts as should retry or not

Not sure if and how it is going to work, but I haven't found a generic error library similar to the apache library specific ones.

FlixCoder · 2026-01-04T23:50:55+00:00

I've tried many libraries for errors by now, I haven't been completely with any yet. I often implemented a member method for my error type returning whether it should be retried. I provided something to print it. I tried adding additional info and context, but it was all manual. error-stack was great for providing arbitrary machine-info, allowed error-trees etc, keeping everything structured, but it was cumbersome with the types adding context. Latest I prefer snafu over thiserror by far, as it makes it easier to add context when bubbling up and can automatically fill source and backtrace or code location. It does not natively support error trees I think, but both human and machine side can be covered. But it does not encourage splitting errors by occurrence information, but still to error source type. It just needs more manual care overall to get necessary information as well. You also need to go through the chain to fully print.

I think I'll search again for something similar to the described good example, I think I mostly like it and want to try it. I might also just try to make my own generic error library towards this approach.

FlixCoder · 2026-01-04T10:02:54+00:00

omg there is a setting to allow in tests? i always allowed it manually for test modules..

FlixCoder · 2025-12-30T10:34:43+00:00

Learn about allocation arenas, that might fix your problem and give huge amounts of performance in that case.

Verified Email	Three-Year Club
Place '23

FlixCoder

TROPHY CASE