@kkrolczyk

1 Followers
0 Following
37 Posts

To be perhaps more explicit what I mean:
This appears to have a language set, outside of the ones I configured to be shown.

Also, side-note; it appears that browser web view simply doesn't show if the post has any language set or not at all.

Both mobile apps show the lang "v" as if it was set for that particular post. Strangely, web view - does not (which is probably why the post appears in the first place).

I'm guessing maybe apps follow some older protocol version, otherwise they'd need to detect the language themselves, and I don't think they do that. Anyways, slightly disappointing.

Obviously you can't force the people to set proper language for a post, and everyone can make a mistake.
That applies to case 1 tho, not 2

How come, despite having language filters configured for my account, I'm still seeing some toots from other (not selected) languages too?

It isn't the case of one writing a post in language X and setting it (incorrectly) to be Y (or not setting it at all) - in such case they will show up, obviously.

It's the case of having, for example languages x/y/z enabled, watching a tag, and post in language v appears.

Happens rarely, but in two separate apps. Both show lang v 1/2

#question #mastodon

Ps, zanim ktoś się niepotrzebne uruchomi, że olaboga lifetimes, ownership itd, tak, tak. Wiem, dzięki.
Po prostu fajnie by było gdyby działało :)

Tzn np gdyby `fn pp<AsRef<[u8]>>(d: &T) { /* pretty print stuff */ }`
Nie wymagało dodatkowych 2 naciśnięć klawiszy, w
```
fn main() {
let x = X(...)
// pp(x); // nope
pp(&x); // no dobra
}
```

Skoro domknięcia(closures) mogą sobie "wybierać" co zrobią (`|| print!("{:?}",avec)` vs `|| avec.push(1)`) imho funkcja też by mogła ;)

Czasem człowiek by chciał by niektóre rzeczy w #Rustlang działały inaczej. Weźmy niektóre automatyczne działania jak auto-deref czy auto-borrow.
Np mamy
struct X(Vec<u8>);
impl X {
fn eat(self) {}
fn use(&self) {}
}

To spokojnie `let x = X(vec![0xFF]); x.use(); x.eat();` rozwikła gdzie użyć referencji a gdzie obiektu. Podobnie gdy funkcja jako parametr przyjmuje dyn np &dyn Display, a przekazujemy d(&zupa). Natomiast nie ma auto-borrow w przypadku np d(zupa) gdyby d<T: AsRef<[u8]>>(s: &T) {}

2/2
What if I later wanted to find a post; is it in favs or boosted? Or is it maybe my answer to a post I wanted to revisit, and I remember only vaguely what was it? I find it all unfortunately quite clunky. There are also posts I am happy to see, but don't intend to come back to them, like a nice news, some cheer-me-up phrase, somebody's introduction post.

PS. Post limit has obviously reasons, but how come apps rarely offer to split into chunks, and I need to perform copy-paste dance?

I wonder if it's just my thing, or some more people'd wish for better "tagging" & "liking" system here in #fediverse / Mastodon. I always need to think hard, maybe overthink #1stworldproblems, should I add to favorites ("like"), boost or bookmark. Eventually, I think I resort to boosting when I think sth might be interesting or funny for others too; bookmark things I see as interesting, but unlikely for others to be curious about. But this strategy is full of flaws. What if it's both? 1/2
... 2/2 to do next, how to continue development (and partially by lack of manpower), stay in limbo for months or years. And some serve important purpose of aligning projects like cortex-m, heapless or embedded hal crates. Certainly it has touched the matter, that whatever comes first - even if not yet ready - as long as it sees commits and some time invested, often wins, and stays. Even if better solution came - it won't be able to break through the old, widely used one. (Caveat, not always!)
I found https://boxyuwu.blog/posts/an-incoherent-rust
an interesting read. It's partially touching the matter of 3rd party crates (as opposed to being part of the language) competing, and more often than not - enforcing "ecosystem" development towards certain direction.
What it does not mention, but has been already noticed by #embedded #rustlang surveys and reports is name-squatting and multiple runtimes, for example async. What it could also touch is, how some crates, due to opinionated ideas about what... 1/2

Gave a talk about halo2 at a Rust meetup in Kraków last month. Got 10 questions from Rust devs trying to figure out zero-knowledge proofs.

I wrote them all up with detailed answers.

https://rustarians.com/10-questions-from-a-zk-meetup-in-krakow/

#rustlang #zeroknowledge #cryptography