Artem

The «mixins» example went more complicated to read. That breaks the idea about readability that you has mentioned. Remove `usingnamespace` maybe not such bad idea. But there is some use-cases...

I need to clarify that the readability for other people could be not that you maybe assume. Generally speaking there is two type of developers. First type is usually write...

Case of `usingnamespace switch` and `Conditional Inclusion` creates a code that could went worse in some cases. Because of converting one fully controlled switch into the group of splitted switches...

Maybe a `mixin` keyword is a right word for `usingnamespace` behavior inside struct. Maybe even `@mixin(some_type)`. Because in example `counter: CounterMixin(Foo, "counter") = .{},` we need duplicate name of variable...