Skip to content

Conversation

@TApplencourt
Copy link
Contributor

TranslationUnit.reparse will now throw an exception when an error occurs. Previously, errors were silently ignored.

@llvmbot llvmbot added the clang Clang issues not falling into any other category label Dec 22, 2025
@llvmbot
Copy link
Member

llvmbot commented Dec 22, 2025

@llvm/pr-subscribers-clang

Author: Thomas Applencourt (TApplencourt)

Changes

TranslationUnit.reparse will now throw an exception when an error occurs. Previously, errors were silently ignored.


Full diff: https://github.com/llvm/llvm-project/pull/173301.diff

1 Files Affected:

  • (modified) clang/docs/ReleaseNotes.rst (+2)
diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst
index ba14a50c1f177..33d0520d15b38 100644
--- a/clang/docs/ReleaseNotes.rst
+++ b/clang/docs/ReleaseNotes.rst
@@ -179,6 +179,8 @@ Clang Python Bindings Potentially Breaking Changes
 - Allow setting the path to the libclang library via environment variables: ``LIBCLANG_LIBRARY_PATH``
   to specifiy the path to the containing folder, or ``LIBCLANG_LIBRARY_FILE`` to specify the path to
   the library file
+- ``TranslationUnit.reparse`` will now throw an exception when an error occurs.
+  Previously, errors were silently ignored.
 
 What's New in Clang |release|?
 ==============================

@TApplencourt TApplencourt changed the title [libclang/python] Add release notes for reparse throwring [libclang/python] Add release notes for reparse throwing Dec 22, 2025
@Endilll Endilll merged commit 82738e4 into llvm:main Dec 22, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clang Clang issues not falling into any other category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants