The current vibe / stance of using .gyb in stdlib

Recently I have noticed a reduction of .gyb files in stdlib.

Is using .gyb frowned upon lately and the community is moving in favor or a pure swift approach?
I personally found gyb useful so far but I can also understand the point of view of favoring more verbose code at the benefit of simplicity.

I apologize if this has been discussed recently, in that case if someone could post a link or two that would be awesome.

1 Like

Most of the removal of gyb in the stdlib has been as a result of the language becoming expressive enough to remove the boilerplate directly, but yeah, non-gyb is preferable where practical.

3 Likes
Terms of Service

Privacy Policy

Cookie Policy