You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**** Templates that took longest to instantiate:
1079 ms: std::variant<sf::Event::Empty, sf::Event::Closed, sf::Event::Resized... (18 times, avg 59 ms)
961 ms: std::__detail::__variant::_Variant_base<sf::Event::Empty, sf::Event:... (18 times, avg 53 ms)
...
**** Template sets that took longest to instantiate:
1582 ms: std::vector<$> (740 times, avg 2 ms)
1273 ms: std::unique_ptr<$> (115 times, avg 11 ms)
...
It would be nice if we could somehow figure out where the bulk of these instantiations come from. For example, it would be useful if the report showed something like the following:
1079 ms: std::variant<sf::Event::Empty, sf::Event::Closed, sf::Event::Resized... (18 times, avg 59 ms)
- 12 times in Foo.cpp
- 6 times in Bar.cpp
...
**** Template sets that took longest to instantiate:
1582 ms: std::vector<$> (740 times, avg 2 ms)
- 420 times in Baz.cpp
- 320 times in Abc.cpp
...
Not sure how feasible/difficult this would be to implement.
The text was updated successfully, but these errors were encountered:
In the report, we can see:
It would be nice if we could somehow figure out where the bulk of these instantiations come from. For example, it would be useful if the report showed something like the following:
Not sure how feasible/difficult this would be to implement.
The text was updated successfully, but these errors were encountered: