The optimizing reason might not be the full explanation, but it still is a realistic downside. Patterns that work on one case go completely flat in another because of performance and as a user you have no clue why. Then the exercise becomes to use magic to guide the optimizer to do the right thing.

Do you want the string representation of the access path? So, a.b.c as “a.b.c”?

To be able to give more meaningful advice, a concrete example in Go would help a lot to understand what you want and what isn’t currently working.

Dataflow can help you to determine if a literal reaches a certain program location , for example as an argument to the method Join, so it shouldn’t matter too much how messy the code is.

The resulting string value is a runtime value. So getting the resulting string value is only possible if it is constructed from literals, but you have to implement that logic yourself.

If you are interested in how a result is used then can use the call which represents the result of the call.