serenity - The Serenity Operating System 🐞

Age	Commit message (Collapse)	Author
2022-06-13	AK/ByteBuffer+Everywhere: Handle errors in ByteBuffer::slice()	Matthias Zimmerman

2022-04-01	Everywhere: Run clang-format	Idan Horowitz

2022-01-24	Everywhere: Convert ByteBuffer factory methods from Optional -> ErrorOr	Sam Atkins
	Apologies for the enormous commit, but I don't see a way to split this up nicely. In the vast majority of cases it's a simple change. A few extra places can use TRY instead of manual error checking though. :^)
2021-09-06	Everywhere: Make ByteBuffer::{create_*,copy}() OOM-safe	Ali Mohammad Pur

2021-05-31	AK: Replace ByteBuffer::grow with resize()/ensure_capacity()	Gunnar Beutner
	Previously ByteBuffer::grow() behaved like Vector<T>::resize(). However the function name was somewhat ambiguous - and so this patch updates ByteBuffer to behave more like Vector<T> by replacing grow() with resize() and adding an ensure_capacity() method. This also lets the user change the buffer's capacity without affecting the size which was not previously possible. Additionally this patch makes the capacity() method public (again).
2021-05-14	LibCrypto+LibTLS: Avoid unaligned reads and writes	Ali Mohammad Pur
	This adds an `AK::ByteReader` to help with that so we don't duplicate the logic all over the place. No more `(const u16)` and `(const u32)` for anyone. This should help a little with #7060.
2021-04-22	AK+Userland: Use mpfard@serenityos.org for my copyright headers	Ali Mohammad Pur

2021-04-22	Everything: Move to SPDX license identifiers in all files.	Brian Gianforcaro
	SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt *
2021-02-23	Everywhere: Rename ASSERT => VERIFY	Andreas Kling
	(...and ASSERT_NOT_REACHED => VERIFY_NOT_REACHED) Since all of these checks are done in release builds as well, let's rename them to VERIFY to prevent confusion, as everyone is used to assertions being compiled out in release. We can introduce a new ASSERT macro that is specifically for debug checks, but I'm doing this wholesale conversion first since we've accumulated thousands of these already, and it's not immediately obvious which ones are suitable for ASSERT.
2021-01-12	Libraries: Move to Userland/Libraries/	Andreas Kling