/cc @robpike

For the exact thing you're asking, this is reasonable, but the general problem is the one that is more useful and more intricate that the Stringer problem. The mapping is not a bijection because of duplicate values, an issue that is straightforward to address if one uses a map but Stringer tries hard to be very dense, data-wise. That requires some thought.

The exact name of the Go symbol is useful only in a narrow context unlikely to be relevant to users. Are "Aspirin" and "aspirin" the same? What about "ASPIRIN"? What about " Aspirin"? And so on. The answers to these questions will vary with the program and programmer. And as you mention, there is the question of how to handle erroneous values. Attempting to have Stringer address them will open a configuration can of worms that will take it far from its original purpose, which was a simple, well-defined tool that demonstrates the use of go generate.

So we're tipping into issues about cases and folding and white space and data structures and so on. This is not a flag for Stringer, this is a new tool.

Thanks a lot for your time and explanation.

Now that I know the original purpose of the stringer tool (a simple, well-defined tool that demonstrates the use of go generate) and after thinking about the implementation details of my proposal, it may go out of that simple goal.

However, what I would really dislike is to have another tool just to generate the counterpart of stringer: it would duplicate de number of go generate calls, the number of generated files, etc.

So I will create a tool that extends the stringer functionality adding what I proposed.

Thanks again and keep making Go more awesome than it already is ;-)

For the record, here is the tool I finally created: https://github.com/alvaroloes/enumer

It's a fork of the Stringer tool, but adding the code to generate the "String to enum value" function and fixing all the test to make them pass.
If finally uses a map, but avoids generating new strings: it uses slices leveraging the variables already generated by the original Stringer code.

As I can't use the github "fork command" to fork only the Stringer tool, I had to copy and paste the code and then do the needed modifications. @robpike Please tell me if you have any inconvenience with that.

Thanks!