Timothy Flynn 68947d55d9 LibIPC: Do not require constructing containers when sending IPC messages ... For example, consider the following IPC message: do_something(u64 page_id, String string, Vector<Data> data) =| We would previously generate the following C++ method to encode/transfer this message: void do_something(u64 page_id, String string, Vector<Data> data); This required the caller to either have to copy the non-trivial types or `move` them in. In some places, this meant we had to construct temporary vectors just to send an IPC. This isn't necessary because we weren't holding onto these parameters anyways. We would construct an IPC::Message subclass with them (which does require owning types), but then immediate encode the message to an IPC::MessageBuffer and send it. We now generate code such that we don't need to construct a Message. We can simply encode the parameters directly without needing ownership. This allows us to take view-types to IPC parameters. So the above example now becomes: void do_something(u64, StringView, ReadonlySpan<Data>);		2025-03-09 11:14:20 -04:00
..
Android	LibTLS: Remove unused DefaultRootCACertificates	2025-02-17 19:52:43 +01:00
AppKit	UI/AppKit: Do not rely on the implicit URL constructors	2025-03-04 16:24:19 -05:00
cmake
Headless	LibIPC: Do not require constructing containers when sending IPC messages	2025-03-09 11:14:20 -04:00
Icons
Qt	UI/Qt: Do not rely on the URL implicit constructors	2025-03-04 16:24:19 -05:00
.gitignore
CMakeLists.txt	Meta: Link with OpenSSL explicitly	2025-02-17 12:36:26 +01:00
DefaultSettings.h
Info.plist