Jonathan Coates 133b51b092 Don't warn when allocating 0 bytes ... I was able to reproduce this by starting two computers, and then warming up the JIT by running: while true do os.queueEvent("x") os.pullEvent("x") end and then running the following on one computer, while typing on the other: while true do end I'm not quite sure why this happens. It's possible that once the JIT is warm, we can resume computers without actually allocating anything, though I'm a little unconvinced. Fixes #1672		2024-01-08 21:52:30 +00:00
..
common	Mark "check valid item" test as required	2024-01-07 13:35:38 +00:00
common-api	Replace several Guava classes with Java stdlib	2023-10-11 09:59:55 +01:00
core	Don't warn when allocating 0 bytes	2024-01-08 21:52:30 +00:00
core-api	Allow generic sources to have instance methods	2023-11-22 10:06:11 +00:00
fabric	Require Minecraft 1.20.1	2024-01-08 21:33:55 +00:00
fabric-api	Publish Fabric jars to CF/Modrinth	2023-03-15 23:20:13 +00:00
forge	Add command computers to the operator blocks tab	2024-01-03 18:42:31 +00:00
forge-api	License CC:T according to the REUSE specification (#1351)	2023-03-15 21:52:13 +00:00
lints	Flesh out MemoryMount into a writable mount	2023-09-29 22:15:23 +01:00
standalone	Allow local domains in the standalone emulator	2023-12-20 17:43:08 +00:00
web	Bump CC:T to 1.109.1	2023-12-16 19:09:39 +00:00
ARCHITECTURE.md	Add a standalone CC:T UI	2023-10-28 17:58:11 +01:00