Homebrew
yalantinglibs 1.2.0
Looks like a template arg list is required now after the template keyword, probably due to https://github.com/llvm/llvm-project/pull/80801. Probably need some changes similar to https://github.com/llvm/llvm-project/pull/94204 in the area where the error occurred.
The error occurs in the vendored copy of iguana in include/ylt/standalone/iguana - this copy is built against, but not installed into the final prefix.
The error is already fixed in the most recent release of iguana via https://github.com/qicosmos/iguana/commit/ef8150869c8a7b45f3416531d67531e0a64c32d7. The newest release of iguana also seems to ship a copy of vendored ylt (in the ylt subdirectory).
It's unclear to me how best to resolve this issue. Which project depends on which? Both seem to be vendoring a copy of the other.
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.
The error occurs in the vendored copy of
iguanaininclude/ylt/standalone/iguana- this copy is built against, but not installed into the final prefix.The error is already fixed in the most recent release of
iguanavia qicosmos/iguana@ef81508. The newest release ofiguanaalso seems to ship a copy of vendoredylt(in theyltsubdirectory).It's unclear to me how best to resolve this issue. Which project depends on which? Both seem to be vendoring a copy of the other.
just dropped a note about the patch in the upstream pr, https://github.com/alibaba/yalantinglibs/pull/947
:robot: An automated task has requested bottles to be published to this PR.
Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.