Fix parsing #56
Fix parsing #56
Conversation
|
the author seems no response? @thvdveld will you fork a new project and release another crate? |
|
@gftea indeed, however, @japaric seems to be working on other projects. So we should give him some time. In the meantime, you can just use my branch. I'm not really going to maintain it and release another crate. However, I made some changes to the project, such as emitting a table in the terminal and allow the wrapper to catch builds from But do not consider this rewrite to be a maintained fork 😉 @japaric thank you for creating this project! It helps me a lot in my research. Are you planning to maintain this? |
|
thanks for the ping! I missed the notification about this PR. also, thanks for the fix! bors r+ |
56: Fix parsing r=japaric a=thvdveld This commit fixes some parsing errors I had. Maybe this fixes #22, #28, #32 and #33. Parsing is fixed for my own project, though I still have logged errors (at least the dot file is generated): ``` [2022-04-28T15:23:33Z ERROR cargo_call_stack] BUG? no callees for `void ({}*)` [2022-04-28T15:23:33Z ERROR cargo_call_stack] BUG? no callees for `void ({}*, void ({}*)*)` ``` Co-authored-by: Thibaut Vandervelden <[email protected]>
|
CI passed but not sure why bors didn't automatically merged the PR. merging manually. |
|
release v0.1.7 includes this fix |
|
Timed out. |
This commit fixes some parsing errors I had.
Maybe this fixes #22, #28, #32 and #33.
Parsing is fixed for my own project, though I still have logged errors (at least the dot file is generated):