You’re conflating paradigms with idioms.
Go and Rust have different idioms and syntax. But they occupy broadly similar paradigms.
For example, you don’t need to relearn how to do iteration like you would with a logic or pure functional language. You wouldn’t need to concepts like methods, like you would if you were coming from a stack based language. Etc
They might share some paradigms (focus on low level optimization) but they aren't the same.
Go focuses on heavy runtime, looser type systems, and all the benefits and drawback that brings.
I think this comment weasels around the intent of the poster without acknowledging their meaning.
Go and rust have very little in common. If you consider them to be the same paradigm that's fine. But I don't think most people would as rust leans more functional.