Corentin Wallez aca8c4a528 Remove the concept of "native_methods" in the generators ... This was used to make the distinction between native-only methods that were those manipulating "natively defined" types, and the rest. Now that all "natively defined" objects are "callback" instead this name didn't make sense. The only relevant thing is that in C there are the Reference and Release methods that don't appear in dawn.json and shouldn't be exposed on C++ objects. Hence most of the native_methods() calls in the templates are updated to be c_methods() calls except for the webgpu_cpp templates that use type.methods directly. BUG=dawn:22 Change-Id: I65c160b8b8a829e4728862c65bc67268a46f445e Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13902 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Jiawei Shao <jiawei.shao@intel.com>		2019-11-22 14:02:52 +00:00
..
ApiObjects.h	Separate WireClient.cpp into multiple files.	2019-01-16 02:18:06 +00:00
ApiProcs.cpp	Remove the concept of "native_methods" in the generators	2019-11-22 14:02:52 +00:00
ApiProcs.h	Remove the concept of "native_methods" in the generators	2019-11-22 14:02:52 +00:00
ClientBase.h	Make the wire Client own ObjectAllocators and CommandSerializer	2019-01-30 02:31:37 +00:00
ClientHandlers.cpp	dawn_wire: Tag deserialize commands with volatile pointer	2019-10-07 20:38:47 +00:00
ClientPrototypes.inc	dawn_wire: Tag deserialize commands with volatile pointer	2019-10-07 20:38:47 +00:00