[RFC] errors.Newf(format string, a ...interface{}) error

[Carlos Cobo]

Hello dear gophers,

I would like to propose an addition to the lonely errors package as stated by the subject of this thread.

What should it do? Equivalent to errors.New(fmt.Sprintf(...)).

As of Go 1.1.2 there are 91 potential uses for this new function according to:
grep --color=auto -iRnH 'Error() string' * | wc -l

What do you think?

-Carlos

[jimmy frasche]

you want fmt.Errorf

[Carlos Cobo]

GOD

DAMN

IT.

That was crazy fast, I'm ashamed of this but I have to admit I wouldn't look for it on fmt, maybe it's just me.

On Friday, August 30, 2013 3:04:35 AM UTC+2, soapboxcicero wrote:

you want fmt.Errorf

[Jesse McNelis]

http://golang.org/pkg/fmt/#Errorf 

--
=====================
http://jessta.id.au

[Kevin Gillette]

I knew about errors.New for months before I found out about fmt.Errorf.

[jimmy frasche]

It's somewhat surprising. The errors package is used a lot and
including Errorf in errors would mean pulling fmt and its dependencies
into pretty much everything.

In the documentation of the errors package the second example is for
Errorf, but then again the example in the package overview uses
fmt.Sprintf with errors.New. The documentation could be clearer, maybe
mentioning fmt.Errorf in the package overview. You could file an issue
to clarify the documentation.

[Jesse McNelis]

On Fri, Aug 30, 2013 at 11:07 AM, Carlos Cobo <toqu...@gmail.com> wrote:

GOD

DAMN

IT.

That was crazy fast, I'm ashamed of this but I have to admit I wouldn't look for it on fmt, maybe it's just me.

That's why there is an example in the errors package.

http://golang.org/pkg/errors/#example_New_errorf

 

--
=====================
http://jessta.id.au

[Carlos Cobo]

Woops, I sent message only to you cause I replied over the phone.

Copy-pasting here:

That's a nice explanation of why it's how it is now.
The clarification as Jeese said is there it was my fault not seeing it (not checking docs, instead let gocode pop out suggestions for me).
Again, ashamed.
I love how well they did think about the language, they should make an even lower level cousin and conquer the world.

[Rodrigo Moraes]

I would like to see a MultiError type in the errors package, which is some boilerplate people write over and over: 

type MultiError []Error

func (e MultiError) Error() string {
    // ...
}

See: https://code.google.com/p/appengine-go/source/browse/appengine/errors.go#33

-- rodrigo

[Kyle Lemons]

On Thu, Aug 29, 2013 at 6:12 PM, jimmy frasche <soapbo...@gmail.com> wrote:

It's somewhat surprising. The errors package is used a lot and
including Errorf in errors would mean pulling fmt and its dependencies
into pretty much everything.

It's the opposite, actually; if you pull in errors, you don't need to pull in fmt; if errors had Errorf, then errors would always pull in fmt.  As it stands, now you only pull in formatted i/o if you use it :).

 

In the documentation of the errors package the second example is for
Errorf, but then again the example in the package overview uses
fmt.Sprintf with errors.New. The documentation could be clearer, maybe
mentioning fmt.Errorf in the package overview. You could file an issue
to clarify the documentation.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[aro...@gmail.com]

This has worked well for me: http://godoc.org/github.com/augustoroman/multierror