Do we still plan to do this?

Yes. Having debugPrint and print do different things leads to a confusing debug experience.

FYI @cbracken who's been in print stuff recently. (Not important, just thought you might like to see.)

Does this still a valid issue?

debugPrint and debugPrintThrottled (its default implementation) have moved from rendering to lib/src/foundation/print.dart and is still a Dart implementation that buffers lines in a list of strings, then schedules periodic flushes.

The intent here is to shift that logic from the framework to dart:ui in the engine so that people writing alternative frameworks could make use of it without having to pull in bits of the Flutter framework. In that sense, the issue is still valid, but given that a vast majority of our users are using Flutter with the framework (and not just dart:ui), this is likely to remain low on our priority list for the time being. Given that we've pulled it out of the render layer and into the foundation layer of the framework, it's probably even lower priority than it once was.

If someone in the community would like to implement this, I'll gladly review it though!

I would like to take this. So what needs to be done is to move the print.dart file to the sky_engine/ui directory?

debugPrint has evolved into a more elaborate API than would make sense to squeeze into print, so I think this is now WONTFIX.

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.