Mike Frysinger

yes, `Args` should always come before `Returns`/`Yields`. `Raises` should be after those.

`GoogleDocstringChecker` does not check ordering. we prob should add that. CrOS's docstring checker does and has for ages fwiw. while not explicitly stated, you can see example docstrings using this...

so your point is def correct that the examples should be using 4 spaces. i think it might be a pain for us to handle internally though :(. we have...

ah, it looks like we do exactly that internally in some examples :(. we duplicate some code examples between internal (2 space) and external (4 space), but we didn't do...

on the unix side, there isn't a great API for terminal emulators. the closest are the [wcwidth](http://pubs.opengroup.org/onlinepubs/9699919799/functions/wcwidth.html) and [wcswidth](http://pubs.opengroup.org/onlinepubs/9699919799/functions/wcswidth.html) functions. they effectively operate on code points. most programs (both terminal...

> Well, they may release resources there, so it would be _nice_ to call the function. i grok the hypothetical, but i question the realistic/practical aspects. i still don't think...

> I haven't checked the amount of resources which would not be freed Looking at the [implementation](https://github.com/strukturag/libheif/blob/33ec3d63470944906dbccffa085970083969de3a/libheif/init.cc#L142), it unloads any loaded external plugins, and clears a colorspace LUT. It doesn't...

afaik, other image formats gd supports don't have these limits, either in reading or writing. i'm not sure we should try to "protect" people from OOM situations, especially when the...

we don't have a style guide. that formatter is the only thing we have. and even its README is clear: > This tool is not yet officially supported by Google....

@dseomn @gpshead FYI