Danilo Bargen

Oh, nice! I guess this whole `v.unknown().assert((value) => value instanceof Uint8Array && value.length === 4)` chain could be packaged into a `uint8ArrayOfLength(number)` helper function to make it more ergonomic, right?...

Cool! Maybe an example like that could be added to the README, under a section like "Custom Helper Functions"? In any case, from my side the helper function approach works...

Yeah, having a way to make the entire object readonly would be useful too, and would save some repetitive typing. I'm not sufficiently familiar with the implementation to be able...

I see your point about the ambiguity. Using both `readonly` (for a single field) and `immutable` (for an entire object) might be a good approach. By the way, doesn't `.optional()`...

Yes, that is correct. As long as the generated `Uint8Array` type is used everywhere, it should be fine, otherwise it's possible that code being tested under NodeJS could start to...

Just as a small bump, I'm also in a situation where a `Sync` threadpool would be useful. The `execute` method takes `&self`, so purely from an ownership point of view...

As a workaround, if it's fine to lock/unlock the mutex for every `.execute()` call, a wrapper like this can be used: ```rust use std::sync::{Arc, Mutex}; use threadpool::ThreadPool; /// A Send...

@bluec0re thanks for the report! This is a bug, this version of the dialog should only be shown for iOS devices (obviously)! 🙂

Hmm, actually I cannot reproduce this. Do you use Play Services or Threema Push? Do you have some steps to reproduce this?

When you put your mobile device into airplane mode and open a conversation, does the iOS-dialog appear as well?