[llvm-branch-commits] [clang] [Serialization] Handle uninitialized type constraints (PR #113182)

falbrechtskirchinger wrote: @cor3ntin @tru This should be added to the 19.X Release milestone, right? https://github.com/llvm/llvm-project/pull/113182 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bi

[llvm-branch-commits] [clang] [Serialization] Handle uninitialized type constraints (PR #113182)

https://github.com/falbrechtskirchinger updated https://github.com/llvm/llvm-project/pull/113182 >From 5025d5a08196392afdbc4f328042795ff93073b9 Mon Sep 17 00:00:00 2001 From: Florian Albrechtskirchinger Date: Mon, 21 Oct 2024 12:24:58 +0200 Subject: [PATCH] [Serialization] Handle uninitialized

[llvm-branch-commits] [clang] [Serialization] Handle uninitialized type constraints (PR #113182)

https://github.com/falbrechtskirchinger updated https://github.com/llvm/llvm-project/pull/113182 >From 5025d5a08196392afdbc4f328042795ff93073b9 Mon Sep 17 00:00:00 2001 From: Florian Albrechtskirchinger Date: Mon, 21 Oct 2024 12:24:58 +0200 Subject: [PATCH 1/2] [Serialization] Handle uninitiali

[llvm-branch-commits] [clang] [Serialization] Handle uninitialized type constraints (PR #113182)

falbrechtskirchinger wrote: The Windows test failures look odd. Could someone please restart the build for me? I want to be sure this isn't just a fluke before I investigate. https://github.com/llvm/llvm-project/pull/113182 ___ llvm-branch-commits mai

[llvm-branch-commits] [clang] [Serialization] Handle uninitialized type constraints (PR #113182)

falbrechtskirchinger wrote: @zyn0217 @cor3ntin, please review. Thank you! (@zyn0217 Note that this PR is targeting `release/19.x`. I've closed #110496 per Corentin's instruction.) https://github.com/llvm/llvm-project/pull/113182 ___ llvm-branch-commi

[llvm-branch-commits] [clang] [Serialization] Handle uninitialized type constraints (PR #113182)

https://github.com/falbrechtskirchinger created https://github.com/llvm/llvm-project/pull/113182 The ASTWriter currently assumes template type constraints to be initialized ((bool)getTypeConstraint() == hasTypeConstraint()). Issues #99036 and #109354 identified a scenario where this assertion