Seth Brenith e620ba139b [torque] Address remaining usages of @noVerifier in base.tq ... For every @noVerifier in base.tq, this change either removes it or ensures that it has some annotation explaining why it can't be removed. The @noVerifier usages that can't be removed fall into the following categories: 1. Classes that don't have their own instance types and therefore have no meaningful way to do an Is...() check 2. Fields that might not exist 3. Fields that are waiting for MaybeObject support in Torque Bug: v8:9311 Change-Id: Id452d4151ec07347ae96a9b5f3b26e2ac8065d31 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1659134 Reviewed-by: Daniel Clifford <danno@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Cr-Commit-Position: refs/heads/master@{#62263}		2019-06-18 22:44:58 +00:00
..
vim-torque	[torque] Address remaining usages of @noVerifier in base.tq	2019-06-18 22:44:58 +00:00
format-torque.py	Reland "[torque] introduce separate implicit parameters for JavaScript calling convention"	2019-06-14 14:02:13 +00:00