From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Vladimir Davydov <vdavydov@tarantool.org>, yaroslav.dynnikov@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2] net.box: add __serialize and __tostring methods for future objects Date: Wed, 25 Aug 2021 00:39:27 +0200 [thread overview] Message-ID: <726cc8fe-c43b-26a3-b810-da7dc9c295fc@tarantool.org> (raw) In-Reply-To: <38b7f8367e68ece293394d9cf88200e7929341de.1629186968.git.vdavydov@tarantool.org> Hi! Thanks for the patch! See 2 comments below. > diff --git a/src/box/lua/net_box.c b/src/box/lua/net_box.c > index 1783da607dcc..3ed464a93437 100644 > --- a/src/box/lua/net_box.c > +++ b/src/box/lua/net_box.c > @@ -1432,6 +1432,29 @@ luaT_netbox_request_gc(struct lua_State *L) > return 0; > } > > +static int > +luaT_netbox_request_tostring(struct lua_State *L) > +{ > + lua_pushstring(L, netbox_request_typename); > + return 1; > +} > + > +static int > +luaT_netbox_request_serialize(struct lua_State *L) > +{ > + struct netbox_request *request = luaT_check_netbox_request(L, 1); > + /* > + * If there are user-defined fields attached to the future object, > + * return them, otherwise push the type name, like __tostring does. > + */ > + if (request->index_ref != LUA_NOREF) { > + lua_rawgeti(L, LUA_REGISTRYINDEX, request->index_ref); > + } else { > + lua_pushstring(L, netbox_request_typename); > + } > + return 1; > +} 1. It does not look good that __serialize might return both a table and a string depending on the object content. Perhaps it is worth to return an empty table when it has no members. Otherwise, say, if I store an optional value in the index and want to get it like this: serialized_req.member then I will get sometimes nil, sometimes an error would be thrown. > + > static int > luaT_netbox_request_index(struct lua_State *L) > { > @@ -2107,6 +2130,8 @@ luaopen_net_box(struct lua_State *L) > > static const struct luaL_Reg netbox_request_meta[] = { > { "__gc", luaT_netbox_request_gc }, > + {"__tostring", luaT_netbox_request_tostring }, > + {"__serialize", luaT_netbox_request_serialize }, 2. You have a whitespace after { in all the other lines. Could you please add them here too? > { "__index", luaT_netbox_request_index }, > { "__newindex", luaT_netbox_request_newindex }, > { "is_ready", luaT_netbox_request_is_ready },
next prev parent reply other threads:[~2021-08-24 22:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-13 12:58 [Tarantool-patches] [PATCH] " Vladimir Davydov via Tarantool-patches 2021-08-13 17:41 ` Yaroslav Dynnikov via Tarantool-patches 2021-08-17 7:58 ` Vladimir Davydov via Tarantool-patches 2021-08-17 8:00 ` [Tarantool-patches] [PATCH v2] " Vladimir Davydov via Tarantool-patches 2021-08-24 22:39 ` Vladislav Shpilevoy via Tarantool-patches [this message] 2021-08-25 13:35 ` Vladimir Davydov via Tarantool-patches 2021-08-25 20:08 ` Vladislav Shpilevoy via Tarantool-patches 2021-08-26 14:56 ` Yaroslav Dynnikov via Tarantool-patches 2021-08-26 15:05 ` Vladimir Davydov via Tarantool-patches
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=726cc8fe-c43b-26a3-b810-da7dc9c295fc@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --cc=vdavydov@tarantool.org \ --cc=yaroslav.dynnikov@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2] net.box: add __serialize and __tostring methods for future objects' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox