writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

339
active users

#RustLang

61 posts55 participants6 posts today
Continued thread

🧵 And now, the part 3 or my series of articles on how to build a #crossplatform #searchengine, in #rustlang.

📰 This article is about how the sharding mechanism works.

💬 Enjoy reading it, feel free to provide me some feedback, here or directly on GitHub 😃

:fediverse: If you enjoy it, feel free to share it on other platforms!

🔗 Here is the link: jdrouet.github.io/posts/202503

jdrouet · Building a search engine from scratch, in Rust: part 3Or how we'll implement sharding and transactions for our search engine.

Hmmm, according to the #Phoronix comments, #Rust #Rustlang is both woke and fascist ...

At least they red-flag themselves so quickly that it doesn't take me long to decide they belong on my block/ignore list

It's a shame, that every new reader of the Phoronix comments is subjected to loads of toxic rubbish

I think I found something weird & scary with `#[target_feature]`. Is this expected?

This feels like it should *at minimum* trigger a lint. How am I supposed to know whether trait impls added extra safety preconditions — especially when using `dyn/impl Trait` and/or an unsealed trait?

Replied in thread

@thezerobit interesting, thanks. I recently began building my first REST API so learning, learning, learning and have GraphQL on my list to look into.

No reason I can't offer both at least in the short term so your comments are welcome.

One issue I guess is the level of support, esp for a novice.

I found a actix + utoipa have helped a lot as I'm coding on a Rust backend. Do you know if there are similar tools to help with #GraphQL+ #Rustlang?