Closed jslee02 closed 4 years ago
Before we suppress this, would it be possible to trace which string function is returning the unspecified template type instead of the fully-qualified template type?
I fully agree with you. Sorry, I should have provided more details.
The intention is actually resolving the issue in the end instead of just concealing it. Supporting the built-in type (#327) is in the path for example. This PR is just to suppress throwing the exception for now. I think we should print a warning saying that the API is ignored as it's not supported yet in the meantime.
At a high level, I would like to extend the chimera features to reasonably support C++ projects with lots of templates. As an example, I tried to use chimera for FCL 0.6, and this segfault the first error I got. :disappointed:
Ok, that makes sense. Perhaps just add that placeholder unit test that shows the problem as per https://github.com/personalrobotics/chimera/pull/329/files#r419865135 and it should be fine to merge.
Related issue: #328