Andrey Kutejko

Recently released Rust 1.67 made things somehow worse. Now [new threads are spawned for every test](https://github.com/rust-lang/rust/pull/107396). This happened to be an old issue. This [stackoverflow question](https://stackoverflow.com/questions/43458194/is-there-any-way-to-tell-cargo-to-run-its-tests-on-the-main-thread) is almost 6 years...

So, `#[gtk::test]` macro makes tests run in the same thread, but this thread is never a main one. That works on Linux and Windows but does not work on macos....

Well, code reuse. Let's say, I want to write a generic widget once and re-use it in a different contexts.

No worries. Readme-files are not always up to date. Some of those resolutions are related to not supported devices. E.g. 320x480 is a resolution of iPhone 1st gen and 640x960...

Cannot reproduce with version `6.0.0-alpha.1`.

Another option to keep ergonomic and flexible builder syntax is to use something similar to [Kotlin's scope functions](https://kotlinlang.org/docs/scope-functions.html). ```rust trait BuilderScopeExt { fn apply(self, scope: &mut FnMut(&Self)) -> Self; }...

@fengalin There will always be specific inconvenient cases. Now it is `Option`, later someone may ask for `property_if_some_deref`, `property_if_ok`, or `property_if_err` etc. I'm just saying, instead of polluting builder scope...