Seth Brenith 25f0e32915 [torque] Make return types required ... Currently, it is possible to declare macros, builtins, etc., without specifying a return type, in which case the return type is treated as void. This is confusing; the code is more clear if we require the return type to be specified. Aside from src/torque, this change is almost entirely just adding `: void` until the compiler is happy. However, two intrinsics in src/builtins/torque-internal.tq have been corrected to declare an appropriate return type. Those two intrinsics were only used in code generated within the compiler after the type-checking phase, so we never noticed that their return types were declared incorrectly. Bug: v8:7793 Change-Id: Ib7df88678c25393a9e3eba389a6a1c4d9233dcbb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3176502 Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#77178}		2021-09-30 15:54:17 +00:00
..
array-sort.tq	[torque] Make return types required	2021-09-30 15:54:17 +00:00
LICENSE	Reland ^2 "[array] Move Array.p.sort to Torque and use TimSort instead of QuickSort"	2018-08-23 15:43:29 +00:00
OWNERS	Remove tebbi from OWNERS and TODOs	2021-01-21 13:23:00 +00:00