Sebastian Wilzbach

@jercaianu try sth. like this: ```d static foreach (T; __traits(allMembers, typeof(impl))) { static if (mixin("isCallable!(impl." ~ T ~ ")") && !T.startsWith("__")) static if (mixin("__traits(getProtection, impl." ~ T ~ ") ==...

Oh and if you use `synchronized` you don't need `assumeUnshared` because the compiler is then smart enough: ```d synchronized(mutex) { return impl.foo(); } ``` (though it needs to be a...

> Regardless, this is liable to break code - what with people using auto and all. Yes in theory that's possible, but isn't this unlikely as the resulting type will...

Yeah sadly the Ocean error seems to be appearing on a few other PRs too.

Disabled it temporarily -> https://github.com/dlang/ci/pull/208 (after the next push, Jenkins should be green again).

Why do we need a new symbol for this? Wouldn't `std.file.write!(WriteMode.newFile)` work too? ---- BTW `std.file.write` should be renamed to `writeFile` or `writeText` as it still can lead to conflicts...

@ibuclaw maybe it's better if you rebase yourself this time?

@ibuclaw would need another rebase.

I'm not entirely sure what the use case for this trait will be, but for those who don't know and as it's a bit related: Vibe.d has the concept of...

> Merge branch 'std.traits.isStronglyPure' of github.com: Please don't use merge commits on your branch - instead `rebase` is recommended: https://wiki.dlang.org/Starting_as_a_Contributor#Rebasing https://wiki.dlang.org/Starting_as_a_Contributor#Squashing https://wiki.dlang.org/Starting_as_a_Contributor#A_file_that_I_made_a_change_on_was_modified_by_a_different_merged_PR.2C_and_now_my_PR_can.27t_be_merged.2C_now_what.3F We also prefer all "fixup" commits to be...