[misc] do not rely on obsolete Riostream.h header and deprecate - #23286
Conversation
|
Squash-on-merge would be okay here? |
For me, always! :) |
Test Results 23 files 23 suites 3d 18h 31m 12s ⏱️ Results for commit 22baf8b. ♻️ This comment has been updated with latest results. |
|
@ferdymercury could you rebase to retrigger the CI? I think the failures are all unrelated but given the many touched files I would still prefer to see more green. |
1657897 to
63437a2
Compare
sure, done! |
63437a2 to
c65d5ea
Compare
c65d5ea to
9699181
Compare
2c08d4a to
7fdcacf
Compare
|
@guitargeek I see some UTF8 errors in the CI, could it be related to the recent textinput upgrade? |
|
Let's see if these are reproducible failures. I've restarted the CI for now. |
Yes they seem to fail always in the same platforms. |
[io] fix header syntax [geom] missing fw declare
64db580 to
22baf8b
Compare
Fixed now, CI is fully green now. Sorry for the noise. |
This Riostream.h header was there 25 years ago when iostream was not yet in the standards.
Use now standard headers, cleaner and more understandable, plus more fine-grained, why should one include three headers when it can just include the needed one.