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

chore: inline non-core formatting args #1520

Closed
wants to merge 1 commit into from

Conversation

nyurik
Copy link
Contributor

@nyurik nyurik commented Feb 4, 2024

Manually inlining format args to make the code more a bit more readable and shorter -- all these args are calling non-core formatting functions like logging, so extra care must be taken to check - just in case the macros were incorrectly implemented (e.g. if a macro has a special case for a literal string without params -- the way panic! was implemented in edition 2018)

Manually inlining format args to make the code more a bit more readable and shorter -- all these args are calling non-core formatting functions like logging, so extra care must be taken to check - just in case the macros were incorrectly implemented (e.g. if a macro has a special case for a literal string without params -- the way `panic!` was implemented in edition 2018)
@@ -113,7 +113,7 @@ fn random_abort() {
pub unsafe extern "C" fn _PG_init() {
#[pg_guard]
extern "C" fn random_abort_callback(event: pg_sys::XactEvent, _arg: *mut std::os::raw::c_void) {
// info!("in global xact callback: event={}", event);
// info!("in global xact callback: event={event}");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

??? why is this line even here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

someone was debugging something? i can delete it if you want

@nyurik
Copy link
Contributor Author

nyurik commented Feb 5, 2024

Closing in favor of #1529, #1530, #1531, #1532

@workingjubilee should I delete that line or not? It is still present in one of these

@nyurik nyurik closed this Feb 5, 2024
@nyurik nyurik deleted the inline2 branch February 5, 2024 22:37
@workingjubilee
Copy link
Member

It can go, yes.

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.

2 participants