[SR-155] REPL: Summary string not being displayed for all struct names about llvm-project HOT 5 CLOSED

Comment by Matthias M. Schneider (JIRA)

If you rename Point to, for example, Pnt then the stuct will be evaluated correctly and printed without producing the error.

from llvm-project.

Comment by Enrico Granata (JIRA)

Hi,
I am one of the engineers that work on the Swift REPL

I can reproduce the issue you're presenting and it is an issue with the LLDB data formatters subsystem

We have a set of builtin data formatters that help us pretty print different data types (for instance, the elements in a Swift array, or the contents of an NSString, ...)
One of those data formatters is for a type named 'Point' that comes from some old Mac OS X framework
It is defined thusly: `(v=${var.v}, h=${var.h})`
In the LLDB formatters syntax, this means that your point shall be printed as the string "(v=" followed by the value of the member "v" of your Point variable, the string ", h=" the value of your Point variable's "h" member, and then a closed parenthesis

In your example, the Point type you defined has neither a ".v" nor a ".h" member, so the LLDB formatter gets confused, and emits a print error instead of just falling back to normal printing

The workaround is to - before defining your Point structure - type at the REPL prompt:

:type summary delete -l objc Point

I can see a few ways to improve this experience here, and I am going to hold on to this issue so that I can actively track these possible avenues

Thanks for your report!

from llvm-project.

Comment by Matthias M. Schneider (JIRA)

Hi Enrico,

thanks for looking into this and the workaround. I would never have thought along those lines given that a newly started REPL session explicitly tells me that Point is an "unresolved identifier" and as such I was happily playing along with the struct using this name. 😉

Your explanation is clear to me and I hope you and the team can fix this issue in the near future.

Cheers,

Mati

from llvm-project.

Comment by Matthias M. Schneider (JIRA)

The issue seems to be solved in snapshot 2016-01-11-a on Ubuntu 15.10.

from llvm-project.

Comment by Matthias M. Schneider (JIRA)

The issue seems to be fixed in current builds of Swift 2.2 and Swift 3.0.

from llvm-project.