Turns out beast::http::request<...> does actually have a constructor taking just the header. I am unsure as to why this wasn't being used but I'm guessing that's part of the reason as to why the code just stopped compiling. In any case, this fix just explicitly calls that constructor before passing it on to the malloy wrapper.
Also I removed the return since its kind of misleading (as the function returns void)
Tectu
commented
2 years ago
fixes: #93
Turns out
beast::http::request<...>does actually have a constructor taking just the header. I am unsure as to why this wasn't being used but I'm guessing that's part of the reason as to why the code just stopped compiling. In any case, this fix just explicitly calls that constructor before passing it on to the malloy wrapper.Also I removed the
returnsince its kind of misleading (as the function returns void)