Are formatting directives required in variadic functions?
In PHP, the variable parameter function is a very convenient function that allows us to use an indefinite number of parameters in the function definition. However, whether you need to use formatting directives in variadic functions depends on your specific needs. Format instructions are usually used to output or process parameters in a specific format. For example, when using the printf() function, you need to specify a format string. If you need to format parameters in a variable parameter function, then of course you need to use formatting instructions. But if you are simply passing parameters to other functions or performing some basic operations, then there is no need to use formatting instructions. In short, whether you need to use formatting instructions in variadic functions depends on specific business requirements.
Question content
I have a variadic function respond
that accepts several positional arguments and propagates an any
slice at the end. The function uses the last parameter differently depending on the context (note how message
and data
differ depending on the value of status
.):
func respond(w http.responsewriter, status int, format string, a ...any) { var ( statusok bool message string data interface{} ) if status >= 300 { statusok = false message = fmt.sprintf(format, a...) data = nil log.error().msg(message) } else { statusok = true message = format data = a[0] log.info().msg(fmt.sprintf("%d", status)) } // issue response responder := render.new() responder.json(w, status, map[string]interface{}{ "statusok": statusok, "status": status, "message": message, "data": data, }) }
I don't get any warnings for the following call:
respond(w, http.statusnotfound, "person %v does not exist", personid)
However, for the next one, the warning respond is called with arguments, but no formatting directive
is raised (but the code runs as expected, person
is a struct
) :
respond(w, http.StatusAccepted, "updated", person)
To my amateur eye, it looks like the variadic function expects a format string at the end and the argument in that format. But why is this so? Are there any limitations on what variadic functions can do?
Or should I better split the responder
into two parts, one for each case ("ok" and "not ok")?
See also https://github.com/golang/go/issues/26486 and https://go.dev/src/cmd/vet/testdata/print/print.go (line 316) for discussion This message in go code (I'm getting a warning from the linter, as @mkopriva and @jimb mentioned in their comments)
WORKAROUND
The warning comes from the linter , because the format string you used when calling the respond()
function does not match the arguments supplied afterwards.
This particular message comes from the printf parser< /a> which logs:
printf: Check the consistency of printf format string and parameters
This check applies to calls to formatting functions such as fmt.printf and fmt.sprintf, and to any detected wrappers for these functions.
Since your response()
function calls fmt.sprintf()
as-is with the format
and a
parameters, this is Think of it as a wrapper around fmt.sprintf()
.
If you want to avoid/get rid of this warning message, the easiest "fix" is to not use these parameters as is, e.g. copy one of the parameters and then pass it:
// Make and use a copy to avoid being marked as a wrapper of fmt.Sprintf format := format message = fmt.Sprintf(format, a...)
The above is the detailed content of Are formatting directives required in variadic functions?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...
