Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

don't do set_new_handler() workaround for LLVM 9+ where it's unnecessary #2276

Merged
merged 1 commit into from
Mar 3, 2024

Conversation

spoonincode
Copy link
Member

See comment in code. There isn't really a problem with the existing code being there afaik, so I suppose this is just adding an indicator to remove this workaround completely once the LLVM requirement is strictly 9+

@spoonincode spoonincode merged commit 006583a into main Mar 3, 2024
26 checks passed
@spoonincode spoonincode deleted the set_new_handler_war_llvm branch March 3, 2024 03:12
@ericpassmore
Copy link
Contributor

Note:start
group: CLEANCODE
category: INTERNALS
summary: Clean separation of code for LLVM versions before (<9) and after (9+). Once Leap's LLVM standard is moved to 9+ set_new_handler() call will be removed.
Note:end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants