Krisztián Szűcs

Well, I'm not sure which one should be the preferred one. Going to rebase them for now.

Strangely github doesn't crosslink discussions here. See the relevant thread at https://github.com/ibis-project/ibis/discussions/4515

We need to rerun the formatter on the current main branch, also we should add the created formatting commit to `.git-blame-ignore-revs`

> @kszucs Are you opposed to this change? Nope, I don't have a strong opinion on this.

Thanks for the updates and the summary, going to have a more thorough look tomorrow.

Would hashing [Node.__getstate__()](https://github.com/ibis-project/ibis/blob/1294b76769888c8e30f8afd8585009d24ab849ad/ibis/common/grounds.py#L141-L142) be sufficient?

Great! Primarly commit level time metrics for open source projects present on GitHub, e.g.: | login | repo | sha | duration[s] | other useful columns... | |----------|------------------|------------------------------------------|-------------|-------------------------| | wakatime...

Is it because of your privacy policy? Honestly I was thinking of something like [GHTorrent](http://ghtorrent.org/), commit level statistics would be a great base for development effort estimation. It could be...

My preference is to use `write_` which triggers computation. I would like to have lazy counterparts eventually which could use `to_` prefix but no strong opinions there. I think methods...

Can you keep around a test case the deprecated builder API?