GHC 2020-06-16

4 comments.

, https://git.io/Jf56S in zmwangx/ets
Worse, buffer might be filled by a long "line" that's really a million lines separated by CRs. We probably want to break on CRs somehow.

, https://git.io/Jf569 in zmwangx/ets
Doesn't work well when command reports progress by rewriting the same line
==========================================================================

Consider this script:

```python
import time

import click

with click.progressbar([1] * 5) as bar:
    for x in bar:
        time.sleep(x)
```

Since we're line-oriented, we do not print anything until the entire loop is finished, and even then no timestamp is visible due to the timestamp being overwritten after the initial CR.

Might be a fundamental limitation, or might be something that could be improved. Food for thought.

, https://git.io/Jf5gV in golangci/golangci-lint-action
Feature request: allow something to the effect of version: latest
=================================================================

Currently, the version parameter must be set to `vx.y`, but golangci-lint releases minor versions pretty rapidly, so for side projects this means the version used on CI is quickly outdated, or one has to babysit the CI very frequently. In fact, the README example is already out of date.

IMO CI is mostly a set-and-forget thing for most people's side projects, and I can't really see the benefit the pinning golangci-lint to a minor release, so this restriction seems to do a disservice.

Would it be possible to support `version: latest` or `version: ^v1.27` or something to that effect?

, https://git.io/Jf5kU in lestrrat-go/strftime
Promote %s to a standard specification?
=======================================

I was writing docs on what strftime specs are supported for a project of mine using this library, so I went to look for where the specs originated. Turns out  they're from FreeBSD[1]/macOS[2] `strftime(3)`: the descriptions match word for word, and the lists of specs are the same with a few specs/categories missing here — POSIX locale extensions (`%E*`, `%O*`), glibc extensions, `%G`, `%g` and `%s`. I can understand not implementing `%G` and `%g`, they're weird (`%G` for 2019-12-31 => 2020), but `%s` is trivial and very widely supported and used, so it's a bit strange it has to be added as an extension, seems more like an accidental omission to me.

So what about promoting it to a standard spec? (The extension could of course be kept around for backward compatibility.) It's an easy change, I can submit a PR if you don't feel like spending time on this.

[1] https://www.freebsd.org/cgi/man.cgi?query=strftime&sektion=3
[2] https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man3/strftime.3.html