Issue by Hixie
Monday Oct 26, 2015 at 21:30 GMT
Originally opened as https://github.com/flutter/engine/issues/1804
We should move the debugPrint() logic in rendering/debug.dart to the C++ side. It does seem to have solved the problem of data loss during high-volume logging.
(Having it on the C++ side, as native behaviour of Dart's print() built-in, would mean that all debug output would be throttled the same way, so people writing new frameworks would get this automatically, and people wouldn't have to import rendering.dart to get it even in regular Flutter apps.)
Monday Oct 26, 2015 at 21:30 GMT
Originally opened as https://github.com/flutter/engine/issues/1804
We should move the
debugPrint()logic in rendering/debug.dart to the C++ side. It does seem to have solved the problem of data loss during high-volume logging.(Having it on the C++ side, as native behaviour of Dart's
print()built-in, would mean that all debug output would be throttled the same way, so people writing new frameworks would get this automatically, and people wouldn't have to import rendering.dart to get it even in regular Flutter apps.)