ocornut / ocornut/imgui_test_engine
File.cpp:line reporting from function calls
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 629
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
i find File.cpp:line incredibly useful in log messages, clicking them in VSCode navigates to that location which is so convenient. if action logs printed them too it would be even better (depending on a test a bunch of actions may run since last IM_CHECK* and then fail, at this point pinpointing exact failure line requires some effort). there is a new C++20 thingy that would allow this without using macros: https://en.cppreference.com/w/cpp/utility/source_location.html
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how action logs are produced and how IM_CHECK* failures report their location. Evaluate the C++20 source_location approach linked in the issue, including the project's language-version support. Done means action logs identify the originating File.cpp:line so failures can be located directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100