Sirraide wrote:
> > @dougsonos I may have some time to look into this since there are probably
> > (as always) some annoying edge cases—particularly w/ templates. Would you
> > be fine with me committing to this branch or would it be easier for you if
> > I made a separate branch for that? Eit
dougsonos wrote:
> @dougsonos I may have some time to look into this since there are probably
> (as always) some annoying edge cases—particularly w/ templates. Would you be
> fine with me committing to this branch or would it be easier for you if I
> made a separate branch for that? Either is
Sirraide wrote:
> a subsequent crash involving lambdas
There definitely is a crash involving templated lambdas on trunk:
https://github.com/llvm/llvm-project/issues/85154
https://github.com/llvm/llvm-project/pull/85147
___
cfe-commits mailing list
cf
Sirraide wrote:
@dougsonos I may have some time to look into this since there are probably (as
always) some annoying edge cases—particularly w/ templates. Would you be fine
with me committing to this branch or would it be easier for you if I made a
separate branch for that? Either is fine by m
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff ad23127222fe23e28ac3deaa16f3ae64d13b7b6f
613f04e311f083c129acaa4598cbfd9894fe3805 --
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Doug Wyatt (dougsonos)
Changes
I pointed out this issue in the review for nolock/noalloc, and @Sirraide opened #85120
Here are some (very rough) bits of code I'd written to try to address the loss
of type sugar, plus a subsequent crash i
https://github.com/dougsonos converted_to_draft
https://github.com/llvm/llvm-project/pull/85147
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
github-actions[bot] wrote:
Thank you for submitting a Pull Request (PR) to the LLVM Project!
This PR will be automatically labeled and the relevant teams will be
notified.
If you wish to, you can add reviewers by using the "Reviewers" section on this
page.
If this is not working for you, it
https://github.com/dougsonos created
https://github.com/llvm/llvm-project/pull/85147
I pointed out this issue in the review for nolock/noalloc, and @Sirraide opened
#85120
Here are some (very rough) bits of code I'd written to try to address the loss
of type sugar, plus a subsequent crash in
