Re: Why does not replace the return value type(i.e. GCobject) of luaC_newobj() function with the type of union GCunion to avoid the explicit cast(i.e. gco2t, gco2p, gco2u and etc)?

Subject: Re: Why does not replace the return value type(i.e. GCobject*) of luaC_newobj() function with the type of union GCunion* to avoid the explicit cast(i.e. gco2t, gco2p, gco2u and etc)?
From: Ranier Vilela <ranier.vf@...>
Date: 2020年10月27日 08:07:47 -0300

Em qui., 22 de out. de 2020 às 23:14, 孙世龙 sunshilong <sunshilong369@gmail.com> escreveu:

Hi, list

Why does not replace the return value type(i.e. GCobject*) of
luaC_newobj() function with the type of union GCunion* to avoid

Are you suggesting creating a new type?

GCunion*

calling the explicit cast(i.e. gco2t, gco2p, gco2u and etc.) and make
the code more concise?

Can you elaborate a small example?

regards,

Ranier Vilela

References:
- Why does not replace the return value type(i.e. GCobject*) of luaC_newobj() function with the type of union GCunion* to avoid the explicit cast(i.e. gco2t, gco2p, gco2u and etc)?, 孙世龙 sunshilong

Re: Why does not replace the return value type(i.e. GCobject*) of luaC_newobj() function with the type of union GCunion* to avoid the explicit cast(i.e. gco2t, gco2p, gco2u and etc)?