Phillip Cloud

I dropped into pdb using this: ``` ❯ python -m pdb -m mkdocs serve > /nix/store/cwsg2cw6yk8yrybyyj0ybg99x6ldd9sl-python3-3.10.9-env/lib/python3.10/site-packages/mkdocs/__main__.py(3)() -> from __future__ import annotations (Pdb) c INFO - Building documentation... INFO - [macros]...

Created some gists, because the logs are huge: 1. [Issue 2](https://gist.github.com/c895db77254c58e2cc82133e9d50243d) 2. [Issue 3](https://gist.github.com/63a5395aeebcba3c10822c2e2040058f)

Is there any way to get rid of the ``` WARNING - mkdocstrings_handlers: 3 aliases were still unresolved after 2 iterations ``` ? We like to build with `mkdocs build...

Thank you for all that you do!

I'm not sure why we should keep select merging around at all. Does it have any non-aesthetic effect or benefit?

> It reduces the query size. Also the user facing compiled query is much more readable with fusing enabled. We don't have any evidence that either of these things is...

Why not wait for issues to come in for the others? If we never have to add these optimizations, then that's code we don't have to maintain/support/test, etc.

I feel pretty strongly about this given all the time and effort we have spent to avoid these bugs from the previous implementation. It seems like if we keep merging...

I'm not saying we should never explore this problem, only that we should avoid enabling optimizations--right before then next release--that we have seen are at high risk for correctness issues...

I took the weekend to think about some of the issues here and did a bit of research on the SQL standard specification of predicate short-circuiting. * According to [this...