You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
During my work I faced unexpected behaviour on calling render.Render() when I was implemented Renderer interface on struct, which occured to be alias. Honestly, I have no clue why it's happening.
But it appears that render calls implicitly some default renderer IN ADDITION to my implementation.
It seems like it should exit here but it does not.
The text was updated successfully, but these errors were encountered:
Archirk
changed the title
render.Render() writes to writer origin data on alias type
render.Render() writes to writer unexpected data of aliased type
May 24, 2024
Hello,
During my work I faced unexpected behaviour on calling
render.Render()
when I was implemented Renderer interface on struct, which occured to be alias. Honestly, I have no clue why it's happening.But it appears that render calls implicitly some default renderer IN ADDITION to my implementation.
It seems like it should exit here but it does not.
Output:
On go-playground
The only way around I have found is setting default responder to empty func. Is this expected way to it?
The text was updated successfully, but these errors were encountered: